From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 58472@debbugs.gnu.org
Subject: bug#58472: [PATCH] Make `message-unique-id' less prone to collisions
Date: Thu, 13 Oct 2022 09:21:05 -0700 [thread overview]
Message-ID: <caa7d03f-68e4-7c24-80c7-e272c456f733@cs.ucla.edu> (raw)
In-Reply-To: <CADwFkmm5A6zbx4=ZSrhcmPjcOR+CT=tRU2fTac-L6XVLLXQdBQ@mail.gmail.com>
On 2022-10-12 19:46, Stefan Kangas wrote:
> The main goal is to avoid collisions, but using the time also gives an
> idea of when the message was sent, which is kind of nice.
That info is in the Date: line, along with zillions of other Received:
lines. There should be no need to repeat it in the Message-ID line.
> Time also
> guarantees a somewhat unique value even if the user has happened to set
> the random seed.
If that's a concern, we should be using more-random data, e.g., with
(base64-encode-string
(secure-hash 'md5 'iv-auto 128 nil t))
if we want 128 bits of randomness (this yields a string like
"B8a3usyu5QSE/rTLu0nIHg==").
As an aside, it's weird that there's no easy way to ask Emacs for an
N-bit random integer, where the randomness is taken from system entropy.
Shouldn't we extend Emacs to support that? E.g., (make-string 128
'iv-auto) could give you an N-byte entropy-derived random string, or
(random -N) could give you an N-bit entropy-derived random nonnegative
integer, or something like that. Then we could write something like this:
(base64-encode-string (make-string 16 'iv-auto))
to get a Message-ID component with 16 bytes (128 bits) of entropy.
next prev parent reply other threads:[~2022-10-13 16:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 16:07 bug#58472: [PATCH] Make `message-unique-id' less prone to collisions Stefan Kangas
2022-10-12 18:08 ` Paul Eggert
2022-10-13 2:46 ` Stefan Kangas
2022-10-13 4:53 ` Matt Armstrong
2022-10-13 12:10 ` Stefan Kangas
2022-10-13 16:35 ` Matt Armstrong
2022-10-13 16:38 ` Paul Eggert
2022-10-14 9:22 ` Stefan Kangas
2022-10-13 16:21 ` Paul Eggert [this message]
2022-10-14 9:22 ` Stefan Kangas
2022-10-16 7:32 ` Stefan Kangas
2022-10-16 17:05 ` Stefan Kangas
2022-10-16 15:19 ` Matt Armstrong
2022-10-16 16:49 ` Stefan Kangas
2022-10-17 6:17 ` Matt Armstrong
2022-10-17 7:30 ` Paul Eggert
2022-10-17 8:14 ` Stefan Kangas
2022-10-17 8:23 ` Eli Zaretskii
2022-10-17 18:47 ` Matt Armstrong
2022-10-17 8:16 ` Eli Zaretskii
2022-10-17 8:29 ` Lars Ingebrigtsen
2022-10-17 8:34 ` Eli Zaretskii
2022-10-17 9:30 ` Stefan Kangas
2022-10-17 11:22 ` Lars Ingebrigtsen
2022-10-17 15:40 ` Stefan Kangas
2022-11-25 1:26 ` Stefan Kangas
2022-10-17 18:40 ` Matt Armstrong
2022-10-18 1:38 ` Paul Eggert
2022-10-18 14:05 ` Eli Zaretskii
2022-10-13 11:45 ` Lars Ingebrigtsen
2022-10-13 12:10 ` Stefan Kangas
2022-10-13 19:15 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=caa7d03f-68e4-7c24-80c7-e272c456f733@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=58472@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).