[Cerowrt-devel] cerowrt-3.7.3-2 released

[Maciej Soltysiak]

I think Dave was thinking of encrypting uftp traffic, which uses RSA. How
random does that have to be?
Depends how sofisticated is your adversary I guess. Do we only want to
prevent clear text transfers or make it hard to decrypt?
On Mon, Jan 21, 2013 at 10:47 PM, <dpreed at reed.com> wrote:

> How random do you need things to be?   Security needs true randomness, but
> there is nothing else I know of where you need "entropy" sources to achieve
> sufficient unpredictability to meet the need of some algorithm.  A simple
> pseudo-random sequence is good enough.
>
>
>
> -----Original Message-----
> From: "Dave Taht" <dave.taht at gmail.com>
> Sent: Monday, January 21, 2013 2:47pm
> To: cerowrt-devel at lists.bufferbloat.net
> Subject: [Cerowrt-devel] cerowrt-3.7.3-2 released
>
>  And is at:
>
> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.7.3-2
>
> + resync with openwrt
> + uftp4 alpha
> + quagga update
> + Hopefully the last ipv6 instruction traps killed (thx ketan and robert!)
> - I see rngd eating a ton of cpu on a given transfer. I'd been meaning to
> look at the quality of the new entropy stuff for ages, and have long hoped
> to be rid of that daemon
>
> After we do a bit more testing I'll tag and push the source to this
> version, and then get cracking on higher layers in the stack again.
>
> A bit about uftp4 support. My intent with getting uftp into cerowrt 18
> months ago was to have an easy multicast test, which would let someone (for
> example) set a rate of 1Mbit and observe what happens to a wireless
> network, observe packet loss at various distances from the AP, etc, as well
> as get a grip on the timing delays induced by the power save mode in wifi
> (basically storing all multicast content and broadcasting it as "content
> after beacon", (CAP, also known colloquially as "crap after beacon"))...
>
> Anyway, while I was thinking that as my basic use case in this project...
>
> Dennis Bush was actually off making a new version do more useful things.
> We got to talking last week... I've tried the ipv4 support and it's nifty.
> Ipv6 didn't work but perhaps my x86 build is bad.
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel at lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/cerowrt-devel/attachments/20130126/18d1879e/attachment-0002.html>