// COMPLETE THREAD

PGP 2.5 is outside...

3 expanded posts ยท every known parent and child

NODE 75ed3e76PGP 2.5 is outside...
Adam Shostack <adam@bwh.harvard.edu>:  
>As I said in my first message, I've heard 2.5 has already found its way
>out of the US.  If that is the case, then the non-US users have access
>to 2.5.  If they do have access to 2.5, then could we discuss the
>technical merits of patching 2.5 v.  patching 2.3?


Lets do a quick check and see where that might be...

> dirs
/alex/edu/cmu/cs/sp/alex/links/security

>gunzip -c < Index.gz | grep -i pgp | grep -v pgpkey | grep 5

/alex/edu/berkeley/csua/ftp/pub/cypherpunks/pgp/pgp25
[...]
/alex/org/eff/ftp/pub/Net_info/Tools/Crypto/PGP/README.PGP2.5
[...]
/alex/edu/umich/eecs/ftp/software/crypt/pgp25src.tar
[...]
/alex/it/unimi/dsi/ftp/pub/security/crypt/PGP/p25.tar


Yup.  Not only is it out, it is FTPable from outside.  

> alex2url /alex/it/unimi/dsi/ftp/pub/security/crypt/PGP/p25.tar

ftp://ftp.dsi.unimi.it/pub/security/crypt/PGP/p25.tar

  -- Vince

(For info on Alex see ftp://alex.sp.cs.cmu.edu/www/alex.html)
NODE 606c34a8Re: PGP 2.5 is outside...
> 
> 
> Adam Shostack <adam@bwh.harvard.edu>:  
> >As I said in my first message, I've heard 2.5 has already found its way
> >out of the US.  If that is the case, then the non-US users have access
> >to 2.5.  If they do have access to 2.5, then could we discuss the
> >technical merits of patching 2.5 v.  patching 2.3?
> Lets do a quick check and see where that might be...
> 

Hmm, recently I received a enourmous amount of diffs, patches and what
so ever, to make pgp 2.3(a) compatible with pgp 2.6 (har)
now were at it, there isn't really a big difference between the two versions
(as far as I can tell) and the little hack from PC does the trick nice.
However you could also do it your self, letting the VERSION_BYTE change
when september 1 1994 is passed.

We'll try to make a nice new PGP 2.3c, which will be 100% compatible with
the 2.6 version. (Bug fixes from 2.3 to 2.4 from Branko Lankester are already
applied, now the compatibility problem will be to let 2.3 know it is 2.6)


--Eric--


"they'll get my crypto key when they pry it from my dead, cold fingers"
 -NSA's (former) chief counsel Stewart Baker

"the NSA being the devious bastards"
 - Michael Handler

 +----------------------------------------+----------------------------+
 | Eric Limpens                           |  Where is my spycamera !?  |
 |                                        |     ..Bart Simpson..       |
 | <Limpe001@hio.tem.nhl.nl>              +----------------------------+
 | S=limpe001;OU=hio;OU=tem;O=nhl;PRMD=surf;ADMD=400net;C=nl           |
 +---------------------------------------------------------------------+


"they'll get my crypto key when they pry it from my dead, cold fingers"
 -NSA's (former) chief counsel Stewart Baker

"the NSA being the devious bastards"
 - Michael Handler

 +----------------------------------------+----------------------------+
 | Eric Limpens                           |  Where is my spycamera !?  |
 |                                        |     ..Bart Simpson..       |
 | <Limpe001@hio.tem.nhl.nl>              +----------------------------+
 | S=limpe001;OU=hio;OU=tem;O=nhl;PRMD=surf;ADMD=400net;C=nl           |
 +---------------------------------------------------------------------+
NODE 11bfabe4Re: PGP 2.5 is outside...
In message <9405251315.AA06738@ next1.tem.nhl.nl >you write:
  > We'll try to make a nice new PGP 2.3c, which will be 100% compatible with
  > the 2.6 version. (Bug fixes from 2.3 to 2.4 from Branko Lankester are already
  > applied, now the compatibility problem will be to let 2.3 know it is 2.6)

Why not have that version advertize itself as 2.6? Then everyone would see
a key that says its 2.6, and which would be legal (under different rules)
worldwide.

Linn H. Stanton <stanton@acm.org>

The above opinions are exclusively my own. If anyone else wants them,
they can buy them from me. Easy terms can be arranged.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6
 
mQCNAi3iC/MAAAEEAOj2cr49PeFwa78Swqf3nBZHspCfZ+IgX8nGU8rbm2oJ6VYj
u8o2M4c3Nv/tkoou24gDtM43/jSrRAalcX40pbGRqWJkkayJ52J8o4KupCrgsKLg
fBE5P4tcUo9KaeJIaOfItJ2qrfTOcFuN7GiyTQ1E2/FGPSHDoqz3kXhxoZcNAAUR
tCFMaW5uIEguIFN0YW50b24gPHN0YW50b25AYWNtLm9yZz4=
=H8OV
-----END PGP PUBLIC KEY BLOCK-----