[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CEB1B PREMEIERE ISSUE
* _IT:_ ftp://ftp.dsi.unimi.it/pub/security/crypt/PGP/pgp26uix.sig
* _IT:_ ftp://ftp.dsi.unimi.it/pub/security/crypt/PGP/pgp26uix.zip
Other sites to look for the above mentioned files at:
This site has most, if not all, of the current PGP files.
(U. S. and Canadian users only)
See /pub/crypto/software/README for the characters for XXXXXXXX
This site has all public releases of the freeware PGP from 1.0 through
/src/security/pgp26uix.zip (MS-DOS executables & docs)
/src/security/pgp26uis.zip (Unix, MS-DOS, VMS, Amiga sources,
docs, info on building PGP into
mailers, editors, etc.)
There are several other versions of PGP
here, including the MIT release.
/mpj/public/pgp/ contains PGP shells, faq documentation, language kits.
/pub/dcosenza -- Some crypto stuff, sometimes includes PGP.
/pub/gbe/pgpfaq.asc -- frequently asked questions answered.
/pub/qwerty -- How to MacPGP Guide, largest steganography ftp site as
well. PGP FAQ, crypto FAQ, US Crypto Policy FAQ,
Steganograpy software list. MacUtilites for use with
MacPGP. Stealth1.1 + other steganography programs.
Send mail to [email protected] with the subject
"Bomb me!" to get the PGP FAQ and MacPGP guide if you
don't have ftp access.
/pub/cypherpunks/pgp (DOS, MAC)
The Amiga version can be FTP'ed from the Aminet in
/pub/aminet/util/crypt/ as StealthPGP1_0.lha.
Also, try an archie search for PGP using the command:
archie -s pgp26 (DOS & Unix Versions)
archie -s pgp2.6 (MAC Versions)
For those individuals who do not have access to FTP, but do have access
to e-mail, you can get FTP files mailed to you. For information on
this service, send a message saying "Help" to [email protected]
You will be sent an instruction sheet on how to use the ftpmail
Another e-mail service is from nic.funet.fi. Send the following mail message
to [email protected]:
This will deposit the two zipfiles, as 15 batched messages, in your mailbox
with about 24 hours. Save and uudecode.
For the ftp sites on netcom, send mail to [email protected] containing
the word HELP in the body of the message.
World Wide Web URLs:
(Thanks to [email protected])
* _UK:_ ftp://ftp.demon.co.uk/pub/pgp/MacPGP/MacPGP2.3.cpt.hqx
* _UK:_ ftp://black.ox.ac.uk/src/security/macpgp2.3.cpt.hqx
* _SE:_ ftp://isy.liu.se/pub/misc/pgp/2.3A/macpgp2.3.cpt.hqx
* _IT:_ ftp://ftp.dsi.unimi.it/pub/security/crypt/PGP/macpgp2.3.cpt.hqx
Requires Think C.
* _UK:_ ftp://ftp.demon.co.uk/pub/pgp/MacPGP/MacPGP2.2src.sea.hqx --
version 2.2 only
PGP is rather counter-intuitive to a Mac user. Luckily, there's a
guide to using MacPGP in
You can, of course, run the DOS version of PGP under OS/2.
ftp://ftp.csn.net/mpj/README.MPJ for the ???????
AMIGA PGP 2.3
* _DE:_ ftp://ftp.uni-kl.de/pub/aminet/util/crypt/PGPAmi23a_3.lha
* _US:_ ftp://ftp.wustl.edu/pub/aminet/util/crypt/PGPAmi23a_3.lha
* _DE:_ ftp://ftp.uni-kl.de/pub/aminet/util/crypt/PGPAmi23a3_src.lha
* _US:_ ftp://ftp.wustl.edu/pub/aminet/util/crypt/PGPAmi23a3_src.lha
* _UK:_ ftp://ftp.demon.co.uk/pub/archimedes/ArcPGP23a
* _US:_ ftp://net-dist.mit.edu/pub/PGP/pgp26doc.zip
* _UK:_ ftp://ftp.demon.co.uk/pub/pgp/pgp26doc.zip
* _US:_ ftp://ftp.netcom.com/pub/mpj/public/pgp/pgp26doc.zip
* _US:_ ftp://ftp.ftp.csn.net/mpj/public/pgp/pgp26doc.zip
These are suitable for most PGP versions. I am not aware of any
export/import restrictions on these files.
* _UK:_ ftp://black.ox.ac.uk/src/security/pgp_german.txt
* _US:_ ftp://ftp.csn.net/mpj/public/pgp/pgp_german.txt
* _US:_ ftp://ftp.csn.net/mpj/public/pgp/PGP_german_docs.lha
* _US:_ ftp://ftp.csn.net/mpj/public/pgp/pgp-lang.italian.tar.gz
* _US:_ ftp://ftp.csn.net/mpj/public/pgp/pgp-msgs-japanese.tar.gz
* _US:_ ftp://ftp.csn.net/mpj/public/pgp/pgp23ltk.zip
* _RU:_ ftp://ftp.kiae.su/unix/crypto/pgp/pgp26ru.zip (MIT version)
* _RU:_ ftp://ftp.kiae.su/unix/crypto/pgp/pgp26uir.zip (ui version)
* _US:_ ftp://ftp.csn.net/mpj/public/pgp/pgp26ru.zip
* _US:_ ftp://ftp.csn.net/mpj/public/pgp/pgp-lang.spanish.tar.gz
* _UK:_ ftp://black.ox.ac.uk/src/security/pgp_swedish.txt
* _US:_ ftp://ftp.csn.net/mpj/public/pgp/pgp_swedish.txt
Some cryptographic software is available from
Read the README file and proceed from there.
Colorado Catacombs BBS
(See also the entry above for PGP 2.6)
(303) 772-1062 Longmont, Colorado (2 lines)
(303) 938-9654 Boulder, Colorado (free call from Denver CO, but 1 line)
For free access: log in with your own name, answer the questions, then
select [Q]uestionaire 3 from the [M]ain menu.
Verified: This morning.
Hieroglyphics Voodoo Machine (Colorado)
Jim Still (aka Johannes Keppler), sysop.
DOS, OS2, and Mac versions.
For free access for PGP, DLOCK, Secure Drive, etc., log in as "VOO DOO"
with the password "NEW" (good for 30 minutes access to free files).
Exec-Net (New York)
Host BBS for the ILink net.
The Ferret BBS (North Little Rock, Arkansas)
(501) 791-0124 also (501) 791-0125
Special PGP users account:
login name: PGP USER
This information from: Jim Wenzel <[email protected]>
If you find a version of the PGP package on a BBS or FTP site and it does not
include the PGP User's Guide, something is wrong. The manual should always
be included in the package. If it isn't, the package is suspect and should
not be used or distributed. The site you found it on should remove it so
that it does no further harm to others.
There are many more sites. You can use archie and/or other "net-surfing"
tools to find a more up-to-date listing, if desired.
- -----BEGIN PGP PUBLIC KEY BLOCK-----
- -----END PGP PUBLIC KEY BLOCK-----
|\ /| | | |
| \/ |o| | Michael Paul Johnson Colorado Catacombs BBS 303-772-1062 |
| | | / _ | [email protected] aka [email protected] [email protected] |
| |||/ /_\ | ftp://ftp.csn.net/mpj/README.MPJ CIS: 71331,2332 |
| |||\ ( | ftp://ftp.netcom.com/pub/mpj/README.MPJ -. --- ----- ....|
| ||| \ \_/ |___________________________________________________________|
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
Section 3: Michael Johnson's PGP bomb contribution.
From: Michael Johnson <[email protected]>
Subject: PGP Time Bomb FAQ
-----BEGIN PGP SIGNED MESSAGE-----
PGP TIME BOMB FAQ
There has been some confusion about the annoying "Time Bomb" in MIT PGP 2.6,
as well as some other PGP version compatibility issues. This is an attempt to
clear up some of that confusion.
WHY IS THERE A TIME BOMB IN MIT PGP 2.6?
In the process of negotiating for the right to distribute a fully legal
version of PGP that the patent assignees agree doesn't infring upon their
patents, MIT agreed to include an inducement for people to upgrade from the
alledgedly infringing freeware PGP 2.3a to the clearly legal freeware MIT PGP
2.6 or the also clearly legal Viacrypt PGP 2.7.
Folks, you may not realize it, but the RSADSI/PKP concession to allow a
freeware PGP in the USA is BIG TIME GOOD NEWS! To induce a small
incompatibility with a downlevel version of PGP with several bugs in it is a
small annoyance by comparison.
WHAT IS THE NATURE OF THE TIME BOMB?
On 1 September 1994 UT, by your system clock, MIT PGP 2.6 will start
generating encrypted message and signature packets with a version byte
(offset 3) of 2 instead of 3. It will accept either 2 or 3 as valid. This
means that messages from PGP 2.3a and old messages from MIT PGP 2.6 can be
read by MIT PGP 2.6, but new messages from MIT PGP 2.6 cannot be read by PGP
2.3a. See pgformat.doc in the MIT PGP 2.6 distribution for the location and
use of these bytes. This time bomb is activated by code in pgp.c that looks
#define VERSION_BYTE_OLD 2 /* PGP2 */
#define VERSION_BYTE_KLUDGE 3
int version_byte = VERSION_BYTE_OLD;
/* Turn on incompatibility as of 1 September 1994 (GMT) */
legal_kludge = (get_timestamp(NULL) >= 0x2e651980);
version_byte = VERSION_BYTE_KLUDGE;
Although a method for disarming the time bomb is obvious to the casual C
programmer, disabling this feature invalidates the RSA license to use the
program, and really doesn't gain you much for reasons that will become
HOW DOES THIS TIME BOMB AFFECT COMPATIBILITY WITH OTHER VERSIONS?
The bottom line is that PGP 2.3a and before (as well as Viacrypt PGP 2.4)
cannot read all of the latest PGP version formats, starting on 1 September
1994. Here is a summary of the version bytes generated and understood:
Version 1 Sep 94 (all times)
- ---------------------------- ----- ---- -----------
2.3 2 2 2
2.3a 2 2 2
Amiga 2.3a.4 2 2 2,3
Viacrypt 2.4 2 2 2
2.6ui 2 2 2,3
MIT 2.6 2 3 2,3
Viacrypt 2.7, pkcs_compat=1 2 3 2,3
Viacrypt 2.7, pkcs_compat=2 2 2 2,3
Viacrypt 2.7, pkcs_compat=3 3 3 2,3
(Not mentioned above is MIT PGP 2.5, which was a buggy beta, nor several
other versions that are outside the mainstream PGP project).
If you are using one of the versions above that cannot understand version
byte 3 messages, you should upgrade to one that does. The upgrade from
Viacrypt PGP 2.4 to Viacrypt PGP 2.7 is only US$10, and also provides several
As you can see, people with downlevel versions of PGP will not be able to
read all PGP messages directed at them, nor will they be able to verify all
of the signed messages they might wish to verify.
It is also worth noting that none of the new versions have any trouble
reading the old format messages.
WHAT IS THE RSA KEY MODULUS LENGTH LIMIT?
The RSA key modulus length limit for compatibility with all mainstream PGP
versions is 1024 bits (military grade). I recommend the use of this length,
at least for now.
PGP 2.3a, running on some platforms (but not others), use to be able to
generate and use 1264 bit keys. In addition, some people have hacked their
own copies of PGP to generate and use longer keys (up to 8192 bits or some
such crazy number). Distribution of these hacked versions under the "Pretty
Good Privacy" trademarked name is not recommended, since it upsets the trade
mark owner (Philip Zimmermann) and interferes with some of his long term
plans to support longer keys in a more organized fashion.
IS 1024 BITS LONG ENOUGH?
Conservative estimates of increasing computing power, advancing mathematical
knowledge, and the propensity of certain spy organizations to spend lots of
money on these things say that 1024 bit keys are strong enough for at least
20 years or so. Less paranoid prognosticators say that such keys are good
for hundreds of years. More paranoid prognosticators think that someone has
already broken RSA and not told us about it, so no RSA key is safe. My
opinion is that RSA keys with a modulus of about 1024 bits in length is more
than adequate to protect most electronic mail and financial transactions.
What do you think?
HOW DOES THE STRENGTH OF RSA AND IDEA COMPARE?
As implemented in PGP, the IDEA cipher used for bulk encryption appears to be
stronger than the RSA cipher. In fact, to strengthen the RSA to the same
level as the IDEA cipher (assuming a brute force attack), it would take an
RSA modulus of about 3100 bits.
WHY NOT ALLOW LONGER RSA KEYS, ANYWAY?
OK, so you are more paranoid than me, and want the RSA key to be at least as
strong as the IDEA cipher. Why isn't there a higher limit to the RSA key
First, there is the minor problem that RSAREF and BSAFE (which are tied to
the RSA patent license for the freeware and some commercial versions of PGP)
have a key length limit of 1024 bits. Changing this involves negotiations
with RSADSI/PKP, and could take some time. Second, allowing longer key sizes
could create a Tower of Babel problem of incompatible PGP versions, since not
all versions could handle these long keys. Third, the implementation of
longer keys needs to be done in an orderly manner such that all mainstream
PGP versions (Viacrypt, MIT freeware, BSAFE-based commercial, and possibly a
non-USA variant) are first upgraded to accept, but not generate, the longer
keys. After all PGP users can accept the longer keys, then PGP versions can
start generating the longer keys with no interruption in service.
It still makes sense to have a length limit for compatibility reasons. I
have asked Philip Zimmermann to increase that to at least 4096 bits when he
can, and I think that he will do that in an orderly manner if there isn't too
much in the way of hassles with RSAREF and BSAFE licensing.
If this isn't secure enough for you, shift to conventional encryption and
manual (direct person-to-person) key exchange, making sure that your keys
have at least 128 bits of entropy. This can be done with pgp -c or another
private key encryption program called dlock that has the virtues of (1) NO
patent problems, and (2) very strong encryption. (DLOCK is not nearly as user
friendly as PGP, but what do you want for free?)
HOW DOES PKCS BYTE ORDERING IN KEYS AFFECT COMPATIBILITY?
PGP versions 2.2 and before generated key and signature block formats with a
different byte order than derived from the PKCS standards. PGP 2.3 also
generated this old format if you specified +pkcs_compat=0 in config.txt or on
the command line. This old format is now obsolete. Unfortunately, the old
format cannot be parsed by RSAREF or BSAFE, so PGP versions based on these
crypto engines (like MIT PGP 2.6) cannot read those packets. Viacrypt PGP,