Gnus development mailing list
 help / color / mirror / Atom feed
From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: Thoughts on Message-ID generation
Date: 01 Mar 2001 19:52:20 -0500	[thread overview]
Message-ID: <m3y9updmbf.fsf@peorth.gweep.net> (raw)
In-Reply-To: <3A9ED357.268858BD@home.com>

* "David A. Cobb" <superbiskit@home.com>  on Thu, 01 Mar 2001
| I'm not sure!  It's about like saying every boson in the universe is an
| object.  So what!  How many bits do we need to count all of them?

More that the idea of treating every bit of information as an object for
all purpose as a panacea is not a good idea.

[...]
| Once we agree on how do I uniquely identify ME,

The fully-qualified domain name of a host is required to be unique.  If it
is not then the host is misconfigured.  Your login on that host is also
required to be unique.  If it is not then accounts are improperly managed.
The time you send a message from a host is close to unique; that run
through MD4 or MD5 along with some random data will be unique.  If you put
them all together you get a very high probability unique identifier,
barring someone deliberately attempting to duplicate it.

Wait... Gnus already does most of that.  I'm not sure if it does the hash
(time + random) bit or just hash (time).

If you insist on going overboard, mash the whole message through MD5 and
use that as the Message-ID string or part of it.

I dunnow about CORBA's security, or lack thereof.  It really isn't an issue
here.  Message-ID is was never intended to be "secure".
-- 
Rat <ratinox@peorth.gweep.net>    \ Do not taunt Happy Fun Ball.
Minion of Nathan - Nathan says Hi! \ 
PGP Key: at a key server near you!  \ 



  reply	other threads:[~2001-03-02  0:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-28 16:05 Toby Speight
2001-02-28 16:31 ` Florian Weimer
2001-02-28 16:38   ` Paul Jarc
2001-03-01 21:39     ` Florian Weimer
2001-03-01 22:46       ` Paul Jarc
2001-03-02 10:34         ` Florian Weimer
2001-03-02 15:03           ` Paul Jarc
2001-03-03 10:45       ` Per Abrahamsen
2001-03-11 14:20         ` Florian Weimer
2001-03-11 15:09           ` Kai Großjohann
2001-03-11 15:10           ` Per Abrahamsen
2001-02-28 18:35   ` Toby Speight
2001-02-28 20:09   ` Kai Großjohann
2001-03-01  3:12     ` Russ Allbery
2001-03-01 14:24   ` Chris Shenton
2001-03-01 14:51     ` Florian Weimer
2001-03-01 22:52       ` Harry Putnam
2001-03-02 10:35         ` Florian Weimer
2001-03-01 15:17     ` Kai Großjohann
2001-03-01 22:05       ` David A. Cobb
2001-03-01 22:38         ` Stainless Steel Rat
2001-03-01 22:55           ` David A. Cobb
2001-03-02  0:52             ` Stainless Steel Rat [this message]
2001-03-02 14:35               ` Toby Speight
2001-03-02 15:41                 ` Stainless Steel Rat
2001-03-02 15:53                 ` Paul Jarc
2001-03-02 16:18                 ` Simon Josefsson
2001-03-02 16:43               ` David A. Cobb
2001-03-02 17:38                 ` Stainless Steel Rat
2001-03-03  3:44                   ` David A. Cobb
2001-12-31  2:37   ` Lars Magne Ingebrigtsen
2002-01-02 23:24     ` Raymond Scholz

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3y9updmbf.fsf@peorth.gweep.net \
    --to=ratinox@peorth.gweep.net \
    /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.
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 NNTP newsgroup(s).