🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

7 total messages Started by bontchev@fbihh.i Thu, 04 Feb 1993 19:32
Posting signed messages
#3855
Author: bontchev@fbihh.i
Date: Thu, 04 Feb 1993 19:32
59 lines
2245 bytes
-----BEGIN PGP SIGNED MESSAGE-----

Date:  4 Feb 93 19:32:42 GMT
Hello, everybody!

As maybe some of you have noticed, since some time I am clearsigning
the articles that I am posting to several newsgroups. Since now with
the availability of PGP there -is- a way to sign an electronic message
(and in the same way to authenticate it), I thought that it is a
matter of politeness to sign my messages.

Unfortunately, this seems to create some problems:

1) It increases the net.traffic.

2) Several sites automatically reject messages containing long
signatures, where a "signature" is considered anything below a line
that begins with two dashes.

3) When transfered to some other networks (e.g., FidoNet), messages
that contain lines beginning with several dashes tend to terribly
confuse the mailing software.

I understand that all this is not my fault, but is due to the fact
that:

1) Some software is badly designed (e.g., a "signature" should be
considered to be delimited by a line, containing -exactly- two
dashes).

2) PGP is not designed with the Internet standards in mind and does
not form messages with proper headers, but instead uses some
delimiters inside the message body.

Nevertheless, in order to avoid further confusion, and until a way to
use shorter signatures is designed, I will stop clearsigning my posts.
This will be the last clearsigned article posted by me, until a better
system is designed. If meanwhile somebody needs to check the
authenticity of some of my articles, please send them to me and I'll
sign them and send them back to you via private e-mail.

Sorry for the inconvenience.

Regards,
Vesselin

-----BEGIN PGP SIGNATURE-----
Version: 2.1

iQCVAgUBK3FxtTZWl8Yy3ZjZAQHn1AQAgnvuaA8bsqj+3Pp2XnN+q4kiGMFJ4aWK
gRhYHWCoi33QDiLmA/i7P4g8XuyWS/HCoIEQgAjhAEq28TEM49kfyDy00ItfTqvV
yLLXYKacvI1FK3EhV2v7Ly3QJEN8IULauu53OeO7aC45ed9hBN4TXibpYznWMTWb
OOTSP7FPZhY=/nDQ
-----END PGP SIGNATURE-----
--
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: Posting signed messages
#3856
Author: warlord@MIT.EDU
Date: Thu, 04 Feb 1993 22:08
40 lines
1599 bytes
> I understand that all this is not my fault, but is due to the fact
> that:
>
> 1) Some software is badly designed (e.g., a "signature" should be
> considered to be delimited by a line, containing -exactly- two
> dashes).
>
> 2) PGP is not designed with the Internet standards in mind and does
> not form messages with proper headers, but instead uses some
> delimiters inside the message body.

Uhh, a couple of things.

1) software shouldn't modify a message, whether it contains a
signature or not (nor whether the signature is plain-text or a
crypto-sig).

2) PGP may not have been designed with the Internet in mind, but PEM
was, and the PEM headers are extremely similar to PGP headers... PEM,
as defined by the new 1113 et.al RFCs define the headers to be:
-----{BEGIN,END} PRIVACY ENHANCED MESSAGE-----

Any ways, if PGP mail is failing because of brain-damaged software,
then I don't see how PEM is supposed to work, either!  Vesselin, my
suggestion to you is to CONTINUE putting your signatures on your
messages.  If I had a better emacs interface (I read mail and news
within emacs) to PGP, I would clear-sign my messages, too.

Please, don't let poorly written gateways detract from the usefulness
of cryptographic authenticity!

-derek

PGP 2 key available upon request, or via AFS:
	/afs/athena.mit.edu/user/w/a/warlord/pgp-pubkey.asc

--
  Derek Atkins, MIT '93, Electrical Engineering and Computer Science
      Chairman, MIT Student Information Processing Board (SIPB)
           MIT Media Laboratory, Speech Research Group
           warlord@MIT.EDU       PP-ASEL        N1NWH
Re: Posting signed messages
#3858
Author: an8729@anon.pene
Date: Fri, 05 Feb 1993 03:41
29 lines
1546 bytes
bontchev@fbihh.informatik.uni-hamburg.de (Vesselin Bontchev) writes:

>2) PGP is not designed with the Internet standards in mind and does
>not form messages with proper headers, but instead uses some
>delimiters inside the message body.

I've seen this misconception in several places.  Actually, the PGP
cleartext signatures have many similarities to the specification in the
Internet standard RFC 1113, which describes Privacy Enhanced Mail
(PEM).  PEM messages start with -----BEGIN PEM MESSAGE----- according
to that RFC.  They will presumably be just as vulnerable to the
problems that Vesselin mentions.  The use of five dashes to start a
line comes directly from this RFC.

The Ascii encoding used in PGP non-cleartext messages also comes from this
RFC.  So does the behavior of quoting all lines which start with "-" by
adding a preceding "- " to them, another behavior which people have called
objectionable.

PGP obviously does not try to be compliant with the PEM RFC's; even
RIPEM doesn't try that.  But it has apparently adopted some of the
ideas expressed there.  People who are unhappy about these provisions
are objecting several years too late.

Hank
-------------------------------------------------------------------------
To find out more about the anon service, send mail to help@anon.penet.fi.
Due to the double-blind system, any replies to this message will be anonymized,
and an anonymous id will be allocated automatically. You have been warned.
Please report any problems, inappropriate use etc. to admin@anon.penet.fi.
Re: Posting signed messages
#3859
Author: perry@jpunix.com
Date: Fri, 05 Feb 1993 12:14
29 lines
916 bytes
-----BEGIN PGP SIGNED MESSAGE-----

In article <WARLORD.93Feb4170855@toxicwaste.mit.edu> warlord@MIT.EDU (Derek Atkins) writes:
>Please, don't let poorly written gateways detract from the usefulness
>of cryptographic authenticity!
>
>-derek
>
>PGP 2 key available upon request, or via AFS:
>	/afs/athena.mit.edu/user/w/a/warlord/pgp-pubkey.asc


Here! Here! I agree 100%! Maybe if enogh people clearsign their
messages, the authors of the supposed breaindead mailer packages would
get the hint.

-----BEGIN PGP SIGNATURE-----
Version: 2.1

iQCVAgUBK3JaDVoWmV4X/7GZAQGiOAP8Dw4Yf7wNoeh4z62PQ6zUEFqi25TlXk3w
lrOzO4xGRHjTS8SVucNYH1r8YUyYjbI+OoNEjLW8ca/1D36dSUEETUEnVANwHKqM
rgYFVsSu8EC9NtjCpTVV57drwT/WgTao+OG4m7XZ7OHkCt9wtiKvFS/Ijdyh9luj
8lO3uHgdhNE=HTGD
-----END PGP SIGNATURE-----
--
 John A. Perry  -  perry@jpunix.com
                   jpunix!perry

 PGP 2.1 signature available by fingering perry@phil.utmb.edu
Re: Posting signed messages
#3860
Author: mathew@mantis.co
Date: Fri, 05 Feb 1993 12:30
20 lines
705 bytes
bontchev@fbihh.informatik.uni-hamburg.de writes:
> I understand that all this is not my fault, but is due to the fact
> that:
>
> 1) Some software is badly designed (e.g., a "signature" should be
> considered to be delimited by a line, containing -exactly- two
> dashes).

-- Not even that.  It should be exactly two dashes followed by exactly one
space and a newline.

-- As for Fidonet, if they don't escape the appropriate lines a la RFC 934,
they deserve everything they get.

> Nevertheless, in order to avoid further confusion, and until a way to
> use shorter signatures is designed, I will stop clearsigning my posts.

-- No!  Carry on.  Force the idiots to fix their broken software.


-- mathew
Re: Posting signed messages
#3861
Author: an8729@anon.pene
Date: Fri, 05 Feb 1993 18:41
30 lines
1544 bytes
Marc VanHeyningen <mvanheyn@cs.indiana.edu> writes:
> In yet another of those stupid anonymous posts from the anonymous
>  posting service in Finland which the guy who wrote the software it is
>  running has requested be shut down or restricted, somebody or other said:
>
> >PGP obviously does not try to be compliant with the PEM RFC's; even
> >RIPEM doesn't try that.  But it has apparently adopted some of the
>
> Sure it does.  It doesn't yet include a few things, like certificates
> (but then again, almost nobody has certificates yet anyway.)  Their
> addition is planned.

I'm sorry that I continue to seem stupid to you.  Please correct me if I
am wrong, but it does not seem to me that RIPEM is compliant with the PEM
RFC's.  It does not support some of the PEM fields, and it has made up
some of its own and added them: Recipient-Name, Originator-Name, and
Originator-Key-Asymmetric.

Because of these changes, RIPEM messages cannot be read or created by
PEM software, and PEM messages cannot be read or created by RIPEM
software, as I understand it.

In the RIPEM manual, it says "RIPEM is not really compatible with PEM"
due to these differences.

Hank
-------------------------------------------------------------------------
To find out more about the anon service, send mail to help@anon.penet.fi.
Due to the double-blind system, any replies to this message will be anonymized,
and an anonymous id will be allocated automatically. You have been warned.
Please report any problems, inappropriate use etc. to admin@anon.penet.fi.
Re: Posting signed messages
#3862
Author: g@pizzabox.demon
Date: Fri, 05 Feb 1993 21:15
7 lines
385 bytes
In article <10000.728920991@moose.cs.indiana.edu> Marc VanHeyningen <mvanheyn@cs.indiana.edu> writes:
:In yet another of those stupid anonymous posts from the anonymous
: posting service in Finland which the guy who wrote the software it is
: running has requested be shut down or restricted, somebody or other said:

Really?  Where is this being discussed? - I'd like to hear more.

G
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