[uclibc-ng-devel] Re: (fwd) Fwd: [ICS-VU-638779, CERT/CC VU#473698] Predictable DNS Transaction IDs in uClibc, uClibc-ng [labs-advisory@nozominetworks.com]

Hi,

I agree with you partly, but given that on embedded targets realtime clock is a optional feature enabled/available or otherwise, one needs to provide multiple options, do have a look at the newer patch I had released earlier,

It provides options for either

a) retaining the simple counter logic as existing logic OR

b) use urandom if available (one may have many embedded systems with linux or bsds or so with urandom but not necessarily realtime clock).

c) else try realtime clock if available,

d) if nothing else just use a ever running prng.

In the case of urandom or clock it will be used to seed the prng periodically.