lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 2 Oct 2013 15:40:29 -0400 From: Theodore Ts'o <tytso@....edu> To: Eric Dumazet <eric.dumazet@...il.com>, Tom Herbert <therbert@...gle.com>, davem@...emloft.net, netdev@...r.kernel.org, jesse.brandeburg@...el.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH RFC] random: introduce get_random_bytes_busy_wait_initialized On Wed, Oct 02, 2013 at 07:18:40PM +0200, Hannes Frederic Sowa wrote: > > I agree. I will look if this is easily possible for secure_seq and > syncookies but depending on the data structure and its size it is a much > harder thing to do. I wanted to try the low-hanging fruits first. ;) To use syncookies as an example, you shouldn't need to store all of the old syncookies. Instead, if every 10 minutes or so, you rekey, and you keep both the old and the new secrets around, you could just simply check an incoming TCP packet using first the new key, and then the old key. During the transition window it would take a wee bit more CPU time, but most of the time, it wouldn't cost anything extra in CPU time, and the only extra cost is the space for the old key. >From a security perspective it would be much better if we tried to make all of the places where we draw randomness and somehow try to rekey on a periodic basis. That way, even if the initial value isn't super-secure, that situation will heal itself fairly rapidly. And it also means that even if an adversary can brute-force break a 32-bit secret, they would have to do so within 5 or 10 minutes in order for it to be useful, and even if they could, it would only be useful for a short window of time. I know it won't always be possible, but to the extent that we can do this, it would be a big improvement from a security perspective. Cheers, - Ted -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists