bug#58472: [PATCH] Make `message-unique-id' less prone to collisions

[Paul Eggert]

I've been looking into this and have several patches along these lines. 
None of them address message-unique-id directly yet (I plan to tackle 
this soon) but they do address the general problem area. The basic idea 
is to use a new make-nonce primitive.

I thought I'd email the patches now to see what others think about the 
direction they're headed.

0001-No-need-to-call-w32_init_random.patch
Description: Text Data

0002-Simplify-feedmail-Message-ID-generation.patch
Description: Text Data

0003-Simplify-calc-comb-by-using-random.patch
Description: Text Data

0004-Simplify-calc-prog-by-using-random.patch
Description: Text Data

0005-doc-lispref-numbers.texi-Improve-random-doc.patch
Description: Text Data

0006-New-function-make-nonce.patch
Description: Text Data

0007-Simplify-auth-source-obfuscate-via-make-nonce.patch
Description: Text Data

0008-Simplify-ntml-by-using-make-nonce.patch
Description: Text Data

0009-Improve-randomness-of-server.el.patch
Description: Text Data

0010-Improve-randomness-of-message-canlock-generate.patch
Description: Text Data