NODE ac6dd573PGP 2.5 / PGP 2.6
Tommy the Tourist <nobody@soda.berkeley.edu>Wed, 18 May 94 11:59:04 PDT
I feel that we should stick with PGP 2.5. It makes me wonder when
MIT comes out with version 2.5 and then TWO weeks later decides to scrap it
and go with a new version. WTFO? Something smells wrong here! I say stick
with 2.5 and don't upgrade to 2.6!
------------
To respond to the sender of this message, send mail to
remailer@soda.berkeley.edu, starting your message with
the following 8 lines:
::
Response-Key: ideaclipper
====Encrypted-Sender-Begin====
MI@```&]S^P;+]AB?X9TW6\8WN:^P&2$:G<'CM.^XL(UI)(0XA"*@FT;^`?8\
M05_9?3X9LT68(?"HY91G\H"\(O.7"27L;H0>302V#6U:^E3CT3U%5EL766HC
:3@6;`,2S/8'$0\9OR@)X"G8KG]1SV=<K#C(`
====Encrypted-Sender-End====
NODE 271d3a34Re: PGP 2.5 / PGP 2.6
Dave Otto <dave@marvin.jta.edd.ca.gov>Wed, 18 May 94 12:29:54 PDT
::
Response-Key: ideaclipper
====Encrypted-Sender-Begin====
MI@```&]S^P;+]AB?X9TW6\8WN:^P&2$:G<'CM.^XL(UI)(0XA"*@FT;^`?8\
M05_9?3X9LT68(?"HY91G\H"\(O.7"27L;H0>302V#6U:^E3CT3U%5EL766HC
:3@6;`,2S/8'$0\9OR@)X"G8KG]1SV=<K#C(`
====Encrypted-Sender-End====
:: [nobody says]
> I feel that we should stick with PGP 2.5. It makes me wonder when
> MIT comes out with version 2.5 and then TWO weeks later decides to scrap it
> and go with a new version. WTFO? Something smells wrong here! I say stick
> with 2.5 and don't upgrade to 2.6!
Has anyone checked 2.5? Does the date restriction code exist there as well?
It seems like MIT was planning the 2.6 release from the start. To go to this
amount of trouble while leaving a UN-modified, legal version available
would be counter-productive (unless they are counting on 2.6 flooding 2.5
off the net).
Dave Otto -- dave@gershwin.jta.edd.ca.gov -- daveotto@acm.org
"Pay no attention to the man behind the curtain!" [the Great Oz]
NODE 6ce1f2faRe: PGP 2.5 / PGP 2.6
Al Billings <mimir@illuminati.io.com>Wed, 18 May 94 14:33:19 PDT
On Wed, 18 May 1994, Dave Otto wrote:
> :: [nobody says]
> > I feel that we should stick with PGP 2.5. It makes me wonder when
> > MIT comes out with version 2.5 and then TWO weeks later decides to scrap it
> > and go with a new version. WTFO? Something smells wrong here! I say stick
> > with 2.5 and don't upgrade to 2.6!
>
> Has anyone checked 2.5? Does the date restriction code exist there as well?
> It seems like MIT was planning the 2.6 release from the start. To go to this
> amount of trouble while leaving a UN-modified, legal version available
> would be counter-productive (unless they are counting on 2.6 flooding 2.5
> off the net).
MIT's press release on 2.6 also mentions bugs in 2.5 that have been
pointed out to them. I'm all for liberating 2.5 from MIT but we need to
fix the bugs in it that they fixed in (or are fixing in) 2.6.
Wassail,
Al
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
| Al Billings aka Grendel Grettisson | Internet: mimir@illuminati.io.com |
| Nerd-Alberich - Lord of the Nerd-Alfar | Sysop of The Sacred Grove |
| Admin for Troth, the Asatru E-mail List| (206)322-5450 |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-