[lkml]   [2000]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Using Yarrow in /dev/random
    > In any case, this requires use of a hash function (sha1) and a block
    > cipher (3des). We were going to do a replacement of /dev/random

    I don't think it does _have_ to be 3des, which is approximately the
    slowest and most tedious to implement cipher known to the world. ;-)
    Blowfish would be nicer except for the big tables. If frequent
    re-keying of the cipher is needed, Twofish would be even a better
    choice. Although this isn't standard Yarrow-160 any more, it would
    make for a better implementation IMHO. (A quick look at Schneier's
    paper suggests that this is possible and anticipated by the design.)

    Also consider using the Crypto API from the international kernel
    patch, which already contains some useful cipher implementations.


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 12:41    [W:0.020 / U:4.972 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site