From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/22682 Path: main.gmane.org!not-for-mail From: Hrvoje Niksic Newsgroups: gmane.emacs.gnus.general Subject: X-Pgp is not rfc2015 Date: 21 Apr 1999 02:04:08 +0200 Sender: owner-ding@hpc.uh.edu Message-ID: <87btgiet53.fsf_-_@pc-hrvoje.srce.hr> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035160558 30608 80.91.224.250 (21 Oct 2002 00:35:58 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 00:35:58 +0000 (UTC) Return-Path: Original-Received: from farabi.math.uh.edu (farabi.math.uh.edu [129.7.128.57]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id UAA19429 for ; Tue, 20 Apr 1999 20:08:45 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by farabi.math.uh.edu (8.9.1/8.9.1) with ESMTP id TAB04637; Tue, 20 Apr 1999 19:04:34 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Tue, 20 Apr 1999 19:05:08 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id TAA05513 for ; Tue, 20 Apr 1999 19:04:58 -0500 (CDT) Original-Received: from pc-hrvoje.srce.hr (mail@pc-hrvoje.srce.hr [161.53.2.132]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id UAA19344 for ; Tue, 20 Apr 1999 20:04:48 -0400 (EDT) Original-Received: from hniksic by pc-hrvoje.srce.hr with local (Exim 2.05 #1 (Debian)) id 10ZkUr-0007Aq-00; Wed, 21 Apr 1999 02:04:09 +0200 Original-To: ding@gnus.org X-Attribution: Hrvoje X-Face: &{dT~)Pu6V<0y?>3p$;@vh\`C7xB~A0T-J%Og)J,@-1%q6Q+, gs<-9M#&`I8cJp2b1{vPE|~+JE+gx;a7%BG{}nY^ehK1"q#rG O,Rn1A_Cy%t]V=Brv7h writes: > * Hrvoje Niksic on Tue, 20 Apr 1999 > | What is wrong about it (except for it not being supported by PGP > | itself)? At least it guarantees you the ability to recover the whole > | MIME message. > > The purpose of digital signatures is to validate that a message has been > transmitted without modification. > > Many mail and news systems will append whitespace to messages. Some strip > whitespace. To compensate, following the lead set by the PEM format > standard, PGP marks signed areas with delimiters. Thus, if a message has > whitespace appended or removed, it will not affect the signed area. > > X-Pgp removes those delimiters. I wasn't talking about X-Pgp, but about Michael Elkins' rfc2015, which uses a different mechanism, which also guarantees trailing-whitespace-proofness, only in a different way. Also, I'm not aware of any RFC condoning X-Pgp (but I might be wrong.) > X-Pgp is a 'standard'. It is a *BAD* standard. It's alarming that the X-Pgp brain-damage can be confused with rfc2015.