Which headers are copied in MIC-CLEAR mode?

Thread View: alt.security.ripem

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Vesselin Bontchev Mon, 11 Jan 1993 19:31

#53

Author: Vesselin Bontchev
Date: Mon, 11 Jan 1993 19:31

16 lines
1370 bytes

It is my understanding that RIPEM, in its MIC-CLEAR mode copies some
of the headers of the message inside the area that is signed, in order
to prevent palyback attacks. Right now I am hacking a perl script to
integrate PGP with my e-mail/news software and would like to include
the same feature.

So my question is: which header lines are copied? Obviously, To:,
Date:, and Subject:. Possibly From:. What else?

Regards,
Vesselin
-- 
Vesselin Vladimirov Bontchev          Virus Test Center, University of Hamburg
Tel.:+49-40-54715-224, Fax: +49-40-54715-226      Fachbereich Informatik - AGN
< PGP 2.1 public key available on request. > Vogt-Koelln-Strasse 30, rm. 107 C
e-mail: bontchev@fbihh.informatik.uni-hamburg.de    D-2000 Hamburg 54, Germany

Re: Which headers are copied in MIC-CLEAR mode?

#54

Author: Marc VanHeyningen
Date: Mon, 11 Jan 1993 20:45

33 lines
2142 bytes

Thus said bontchev@fbihh.informatik.uni-hamburg.de:
>It is my understanding that RIPEM, in its MIC-CLEAR mode copies some
>of the headers of the message inside the area that is signed, in order
>to prevent palyback attacks. Right now I am hacking a perl script to
>integrate PGP with my e-mail/news software and would like to include
>the same feature.
>
>So my question is: which header lines are copied? Obviously, To:,
>Date:, and Subject:. Possibly From:. What else?

RIPEM itself is not smart enough to selectively copy some headers and
not others into the plaintext; it will either copy all of them or none
of them.

The perl script I wrote, send-ripem, is more selective.  It includes all
headers except Bcc (which obviously shouldn't be included in the
plaintext) and Fcc (which is only meaningful for MH.)  You may find the
perl code in send-ripem of use; feel free to borrow from it.  (Let me
know if you don't have a copy, I'll gladly send you one.)

(Getting a mailer interface which handles Bcc properly for full-fledged
encryption is more difficult to do, but doable.)

I recommend From:, Date:, and To: at minimum; this is sufficient to
prevent replay attacks (provided the recipient pays attention), and has
the added benefit of making the plaintext an RFC 822 compliant message.
Bcc: is the only header for which I can think of a good reason *not* to
include it in the plaintext.
-- 
Marc VanHeyningen    mvanheyn@whale.cs.indiana.edu    MIME & RIPEM accepted
"I used to sing the blues when I was feelin' so down."
"What do you do now?"
"Post to sci.research.careers."

Re: Which headers are copied in MIC-CLEAR mode?

#56

Author: Mark Riordan
Date: Tue, 12 Jan 1993 00:10

10 lines
985 bytes

Vesselin Bontchev (bontchev@fbihh.informatik.uni-hamburg.de) wrote:
: It is my understanding that RIPEM, in its MIC-CLEAR mode copies some
: of the headers of the message inside the area that is signed...
: So my question is: which header lines are copied? Obviously, To:,
: Date:, and Subject:. Possibly From:. What else?

If the -h i option is in effect (which it normally is), *all*
headers are copied, else none are.  RIPEM isn't selective.

Mark

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads