1992-12-23 - Re: Signing ascii text

Header Data

From: yanek@novavax.nova.edu (Yanek Martinson)
To: karn@qualcomm.com (Phil Karn)
Message Hash: 1cc717baaeb594dd8ac0c3873a11f99a379cd7667cbcc6715f25f7996c01565c
Message ID: <9212230431.AA25182@novavax.nova.edu>
Reply To: <9212230406.AA28094@servo>
UTC Datetime: 1992-12-23 04:32:03 UTC
Raw Date: Tue, 22 Dec 92 20:32:03 PST

Raw message

From: yanek@novavax.nova.edu (Yanek Martinson)
Date: Tue, 22 Dec 92 20:32:03 PST
To: karn@qualcomm.com (Phil Karn)
Subject: Re: Signing ascii text
In-Reply-To: <9212230406.AA28094@servo>
Message-ID: <9212230431.AA25182@novavax.nova.edu>
MIME-Version: 1.0
Content-Type: text/plain


> (e.g., email messages, etc). Is there a convention for the end of line
> sequence that is to be used for the copy of the file that is run through
> the hash function? If there isn't, then the file hash will depend on the

Canonical Text has a CR and LF at the end of each line.  This is 
documented in some RFC.  All (most?) protocols used on internet such
as smtp, finger, etc, use this format.  The possible justification
is that an extra linefeed or a carriage return is not as bad as a missing
one.  

For e-mail you may have other problems, if the messages go through
gateways that like to munge messages.  For example your tabs could
be expanded into spaces, or the other way around.  Some character
set conversions may be done.

Blank lines may be removed or added.


--
Yanek Martinson    mthvax.cs.miami.edu!safe0!yanek     uunet!medexam!yanek
this address preferred -->> yanek@novavax.nova.edu <<-- this address preferred
Phone (305) 765-6300 daytime   FAX: (305) 765-6708  1321 N 65 Way/Hollywood
      (305) 963-1931 evenings       (305) 981-9812  Florida, 33024-5819





Thread