From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: X-Pgp is not rfc2015
Date: 21 Apr 1999 03:47:52 +0200 [thread overview]
Message-ID: <873e1ueoc7.fsf@pc-hrvoje.srce.hr> (raw)
In-Reply-To: Stainless Steel Rat's message of "20 Apr 1999 20:42:37 -0400"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * Hrvoje Niksic <hniksic@srce.hr> on Tue, 20 Apr 1999
> | I wasn't talking about X-Pgp,
>
> I was, and have been since the start of this thread,
No. The message I answered to was your answer to Jari, who said:
Jari> It's not something new...
Jari>
Jari> There is already standard by IETF working group in RFC 2015,
Jari> where the PGP is handled transparently in MIME message.
Jari>
Jari> Title: MIME Security with Pretty Good Privacy (PGP)
Jari> Author: M. Elkins
Jari> Date: October 1996
Jari> Mailbox: P.O. Box 92957 - M1/102
Jari> Los Angeles, CA 90009-2957
Jari> Pages: 8
Jari> Characters: 14,223
Jari> Updates/Obsoletes: None
Jari>
Jari> URL: ftp://ds.internic.net/rfc/rfc2015.txt
rfc2015 is not X-Pgp.
> since validation of X-Pgp was what the original poster wanted.
The original poster (Stefanie Teufel) definitely did not want
validation of X-Pgp -- he wanted to decipher an rfc2015
`multipart/encrypted' message which he even quoted.
(Note that the message Stefanie quoted did contain an `X-Pgp' header,
but it had nothing to do with X-Pgp as advertised by Jari; its MIME
headers clearly marked it as an rfc2015 message.)
next prev parent reply other threads:[~1999-04-21 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-21 0:04 Hrvoje Niksic
1999-04-21 0:42 ` Stainless Steel Rat
1999-04-21 1:47 ` Hrvoje Niksic [this message]
1999-04-21 14:33 ` Stainless Steel Rat
1999-04-21 17:53 ` Hrvoje Niksic
1999-04-21 18:08 ` Stainless Steel Rat
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=873e1ueoc7.fsf@pc-hrvoje.srce.hr \
--to=hniksic@srce.hr \
/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).