For legal reasons we cannot supply PGP directly as this would break certain archaic U.S. laws. However we can tell you how to get it:
For Windows NT :- look for a version for '32-bit DOS...' , you don't need the fancy windows front ends (which do not work without also getting the DOS application) e.g. for the international version I used: ftp://ftp.no.pgpi.com/pub/pgp/2.x/pc/msdos/pgp263ix.zip (U.S. citizens must not use this version apparently)
For Unix:- get the source and build it, typically with a command like:
For NT install PGP 2.6.* rather than 5.0 as the command line utilities are required which weren't available in version 5 last time I checked.
Transfer the file http://ftp.sunet.se/pub/news/misc/pgpcontrol/PGPKEYS.gz , gunzip it and then add these public keys to your key ring, e.g.
gunzip PGPKEYS.gz pgp -ka PGPKEYS
On NT you should define the environment variable PGPPATH for all users (in the system setup) to tell pgp where it can find it's key rings, on UNIX you should run the above commands as the 'NEWS' user and pgp will put the key ring into a directory called, ~news/.pgp/ or you can define PGPPATH in dnews_start.sh
On unix, if you define PGPPATH to point to a directory that is not owned by NEWS then you may find PGP fails because it cannot access the key ring.
This step is only necessary if you have not put 'pgp' into your path.
pgp c:\app\pgp\pgp.exe pgppath d:\app\pgp pgptz gmt (optional and only valid in dnews5.3d and later)
The pgppath variable actually points to where your key ring is stored, on unix this might be something like /var/spool/news/.pgp if you created the key ring for the user 'news' on unix the path matches the home directory for that user plus .pgp, on NT the pgppath just has to match your settings in your pgp config file or in your environment variable.
Note: currently PGP is only implemented on the Windows NT and UNIX version of DNEWS.
copy sample.control (workarea)/pgp.tst tellnews pgp_test tail dnews.log