lkml.org 
[lkml]   [2001]   [Sep]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH][RFC] Allow net devices to contribute to /dev/random
> In any case the following must be true for this to cause problems:
> a) The network must be the primary source of entropy (this
> will be common in the case where the patch is useful)
> b) BadGuy must monitor from time 0 (boot of system) to get
> useful information
> c) BadGuy must have information about what network card the system
> has, or _very_ good statistical information about delay to
> interrupt & timing in general.
> d) BadGuy must have information about how long the processing for
> the interrupt handler takes, as the randomness addition is done
> _after_ all processing. This also causes interesting problems
> for prediction if more than one event is handled at once.
> e) BadGuy must have access to information of network traffic on
> all the networks that are attached to the computer.
>
> Now none of this guarantees security (but then again, very little will
> _guarantee_ security.
>
> I may have missed some stuff here... (caveat emptor)
>

To be constructive: why not make this HMAC-SHA1? The key for HMAC can be fed
through a sysctl interface. This would mean that BadGuy would need knowledge of
the key and thus the key generation method, too, especially if the key is
replaced at varying times and independent of network traffic.


Andreas Steinmetz
D.O.M. Datenverarbeitung GmbH
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:03    [W:0.052 / U:6.064 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site