From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: Signature/encryption, what's the standard ?
Date: 27 Oct 1999 23:42:40 -0400 [thread overview]
Message-ID: <m34sfc2lsf.fsf@peorth.gweep.net> (raw)
In-Reply-To: John Saylor's message of "27 Oct 1999 22:42:00 -0400"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* John Saylor <jsaylor@mediaone.net> on Wed, 27 Oct 1999
| I have never heard of this [but I don't stay up to date on MTA
| technology].
The early version of X-Pgp was quite prone to this. I personally
experienced a 100% failure rate with usenet control messages when it was
first adopted (and then I stopped being a news server admin so I have not
kept up with it).
| Does this kind of thing happen often? Which MTAs are known to exhibit
| this behavior?
Delivery agents that deliver to Unix mbox-style mailbox files might append
a blank line to ensure proper envelope separation. Some POP servers will
do this, too; others will strip *all* trailing whitespace from a message,
all in violation of every mail handling specification as well as POP's
proscription against doing anything but moving messages from point A to
point B.
The purpose of a digital signature is to be 100% positive that such and
such person originated the message. If there is any possibility at all of
a false negative, the system itself is rendered unreliable. The frequency
of false negatives is a measure of the unreliablity of that system.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0e (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE4F8Yvgl+vIlSVSNkRAo1cAKCyGmIWsBUWvHNQtM6QcnhnYizzagCfb5wa
UgsA5pwsdQP51vat0C3noW4=
=x0qR
-----END PGP SIGNATURE-----
--
Rat <ratinox@peorth.gweep.net> \ Happy Fun Ball may stick to certain types
Minion of Nathan - Nathan says Hi! \ of skin.
PGP Key: at a key server near you! \
next prev parent reply other threads:[~1999-10-28 3:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-27 12:57 Oscar Figueiredo
1999-10-27 14:26 ` Alan Shutko
1999-10-27 15:51 ` Hrvoje Niksic
1999-10-27 16:49 ` Oscar Figueiredo
1999-10-28 10:05 ` Hrvoje Niksic
1999-10-28 10:49 ` Graham Murray
1999-10-28 10:52 ` Hrvoje Niksic
1999-10-28 11:51 ` David Kågedal
1999-10-28 11:58 ` Hrvoje Niksic
1999-11-07 0:07 ` Lars Magne Ingebrigtsen
1999-10-29 6:32 ` Steinar Bang
1999-10-29 12:17 ` Simon Josefsson
1999-10-29 15:21 ` Eric Marsden
1999-10-28 1:02 ` John Saylor
1999-10-28 1:38 ` Jason R Mastaler
1999-10-28 7:38 ` Jaap-Henk Hoepman
1999-10-28 2:02 ` Stainless Steel Rat
1999-10-28 2:42 ` John Saylor
1999-10-28 3:42 ` Stainless Steel Rat [this message]
1999-10-30 6:41 ` Florian Weimer
1999-11-01 3:46 ` David S. Goldberg
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=m34sfc2lsf.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).