Article View: alt.security.pgp
Article #82Re: PGP
From: Marc VanHeyningen
Date: Wed, 06 Jan 1993 14:34
Date: Wed, 06 Jan 1993 14:34
43 lines
2641 bytes
2641 bytes
Thus said eoliver@ralph.cs.haverford.edu (Erik Oliver): >RIPEM just ain't as good as PGP, I got a special username password to >download ripem from a site in missouri, (I think it is the creator's >site), and compiled it without much trouble. Michigan, not Missouri (not that it really matters.) >I found that its interface made PGPs look terrific, IMHO. Can you be more specific? What tasks did you find easier to perform using PGP? How exactly did you attempt to perform them with each? RIPEM takes a bit of customization to make work smoothly, and works much better with some mailers than others (which is the fault of the mailer.) >Also, I realized that using it would be a pain in the ass, because >nobody outside the USA and CA would be able to (1) validate my messages >and (2) nobody would be able to decrypt them either. This is true, at least until compliant software ends up in use outside North America. Conversely, with PGP, many potential correspondents in the U.S. and Canada will not be able to decrypt or verify your messages because they believe PGP to be illegal and will not use it. You makes your choices. >Additionally, there are going to be _many_ competing RIPEM >implementations that are not all necessarily going to be compatible. >For example, I am waiting to beta test a version of RIPEM from tis.com. >Perhaps that will be better. I assume that what you actually mean is "there will be many PEM implementations that are not all necessarily going to be compatible." There is a version of PEM from TIS that is being made available. It will not be RIPEM. It should (eventually) be compatible with RIPEM in some way, though the standards are still evolving. But at least there are standards, and RIPEM has a chance in hell of communicating with anything other than another copy of RIPEM, which is more than PGP can say. -- Marc VanHeyningen mvanheyn@whale.cs.indiana.edu MIME & RIPEM accepted Immediate access, limited costs, high-tech medicine. For health care, choose only two of the above.
Technical Details
Message-ID:
<1993Jan6.093413.17974@news.cs.indiana.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!news.cs.indiana.edu!mvanheyn@mango.ucs.indiana.eduReferences:
<1993Jan6.023852.2552@zip.eecs.umich.edu> <1993Jan6.050831.22326@netcom.com> <A2GWB31F@cc.swarthmore.edu>Show Full Headers
Complete Article Headers
Newsgroups: alt.security.pgp,alt.security.ripem Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!news.cs.indiana.edu!mvanheyn@mango.ucs.indiana.edu From: Marc VanHeyningen <mvanheyn@whale.cs.indiana.edu> Subject: Re: PGP Message-ID: <1993Jan6.093413.17974@news.cs.indiana.edu> X-Quoted: 28% Organization: Computer Science Dept, Indiana University References: <1993Jan6.023852.2552@zip.eecs.umich.edu> <1993Jan6.050831.22326@netcom.com> <A2GWB31F@cc.swarthmore.edu> Date: Wed, 6 Jan 1993 09:34:08 -0500 Lines: 43