Since I did release the source code, there are a number of independent efforts going on to create enhanced versions of Private Idaho. Here's some of them:

• Ian Lynagh has added a variety of features I thought about, but never got around to. Check out PIt (the latest version, as of March 4, 1998 is PI3.52t).
• Based on the distributed source code, C.A.T.S. International has a 32-bit version of Private Idaho now available. Entirely new interface with a button bar and other cool features.  Henry Martin is working on PGP 5.0 support.
• Alex Cameron has a 32-bit version that's available here.

Although it may look the same, version 2.8 has a lot of new features. Including:

• Auto encrypt/decrypt of configuration files - If started with the command line PIDAHO.EXE C:\WINDOWS\PIDAHO.INI (or whatever the path of the INI file), PI will PGP decrypt the following files on startup, and decrypt them on exit: PIDAHO.INI, NYMS.TXT, ADDRESS.TXT, and PUBKEYS.OUT. Recommended for high security requirements.
• Support for auto-encrypt/decrypt of PGP's secring and pubring files - Conventionally encrypts the key rings on exit, and decrypts them when PI first runs. This prevents someone from examing your secret key ring to view your nym keys, or your public ring to see who you correspond with.
• Update remailer info command - When connected to the Net, this command downloads the REMAILER.HTM file (a copy of Raph's Web page) and updates current remailer info. This eliminates the RMINO and CPMAILER files and the need to manually update them. If Mixmaster type remailers are selected in the Remailers menu, information is updated about them from Raph's MM page.
• Get remailer keys command - Connects to the remail key page and downloads the contents to the message box. Keys can be added with the Add key from message command.
• Submit key to server command - Submits the public key in the message box to the MIT server via an e-mail message.
• Get key from server command - Attempts to retreive a public key from the MIT server based on the user ID in the To: box.
• Generate key pair command - Support for creating PGP key pairs is now available.
• Load passphrase at startup (in PGP Options) - Prompts for passphrase at start. Keeps in memory so you never need to enter in the DOS box during encrypt and decrypt operations.
• Remailer newsgroup header command - Adds a "Newsgroups" header in the message body to support news gateways such as mail2news@anon.lcs.mit.edu.
• nym.alias.net support - The nym.alias.net nym servers (newnym type) are now supported. An "Edit existing alias.net nym" command has been added once a nym has been created. Creation of this type of nyms works is identical in interface to the alpha nyms. Note: Advanced features such as multiple and probability-based reply blocks are currently not implemented.
• Delete nym command - This command deletes a nym from the NYMS.TXT file and optionally sends a delete message to the nym server.
• Attachment support - Users can now attach files to mail messages. These are encoded as Base 64 MIME compliant. Attachments may be encrypted or not. Note: Remailers and newsgroup postings do not support attachments.
• Keys menu added - A new menu called Keys now supports key related commands.
• Update PUBKEYS.OUT command - Renamed from update public key to be more accurate in meaning.
• Support for private remailers - Remailers that are in operation but are no longer displayed in Raph's pinging list may be listed in a text file named PRIVATE.TXT in the PI directory. Each line should contain only the remailer address. These remailers will be appended to remailers shown in Raph's list.
• X-headers command - Allows user defined headers to be inserted in a mail message.
• Append on send command - When checked, automatically appends remailer info (including encrypting to remailers if selected) to the message before sending. Eliminates the need to manually use the Append info command.
• Transfer options command - To transfer a message to an application, only scripting is supported now. The tabbed, message headers have been eliminated.
• Add system info command - When you use the "Send feedback" command in the Help menu to report a problem, check this menu item first. It adds system and configuration information to the message to help me resolve problems.
• ViaCrypt support removed - Due to compatibility problems in getting PI to work with the 4.0 version of ViaCrypt, and a small user base, support has been removed. ViaCrypt users should simply put a copy of the DOS version of PGP in their PGP directory to continue to use PI.
• Windows online help removed - PIDAHO.HLP is no longer shipped. Users are encouraged to go to: http://www.eskimo.com/~joelm/pihelp.html and use a browser to access the help file. The file can be printed or saved locally if the user wants a copy on their hard drive for reference. The HTML file is distributed with Private Idaho.
• Anon.penet.fi support removed - As of September 1996, Anon.penet.fi is no longer operation. Because of this, support has been removed from PI.
• Font changes - Ugly FixedSys font has been replaced by MS San Serif.
• Under the hood - The IPP20.VBX file is no longer required. The following controls enhance PI's Internet connectivity and performance and should be placed in the C:\WINDOWS\SYSTEM directory: HTTP20.VBX, NETC20.VBX, POP20.VBX, SMTP20.VBX

point and click ease of use 

works with popular commercial and Windows e-mail, Web browsers, news readers

supports PGP message/file encryption, decryption, and signing 

advanced PGP options such as multiple keys and encrypt to self 

PGP key management features 

directly send e-mail through SMTP 

directly receive PGP messages from POP3 mailboxes 

USENET posting from remailers 

support for nym servers

advanced remailer options such as encryption, chaining, latent time, and cutmarks 

supports Cypherpunk, Mixmaster, and Soda anonymous remailers

Private Idaho is free, with no shareware or registration fees. Its purpose is to encourage the wide spread use of strong cryptography and provide users with a greater level of on-line privacy.

The previous version (2.7b1) of Private Idaho was released on 7/24/96. 

If you don't have the VBRUN300.DLL (which Private Idaho and its setup application require), get it here.

Having problems downloading from eskimo.com? Try:

ftp://ftp.rivertown.net/pub/win/privacy/

You can always post a question to the alt.security.pgp USENET newsgroup. In many cases, a Private Idaho user will answer your question.

Wil Ussery has put together some pretty good FAQs on how to use Private Idaho to post anonymously to USENET newsgroups and how to use it with nym servers. Thanks Wil! Much more expanded coverage than I've included in the documentation.

A Private Idaho user's guide in Microsoft Word format is also available as of 10/17/96. Thanks to Luca Venuti - lucven@compumaint.it.

Even though Private Idaho isn't a commercial product, I sometimes get e-mail from people who like it so much they want to contribute to its further development. In the past, I've declined, but after giving it some thought, if you want to support the application, send a donation in the name of Private Idaho to the Electronic Privacy Information Center (EPIC). I personally feel this organization is doing some great things, standing up for a variety of rights that are critical to the continued growth and success of the Internet. Check out their Web page, whether it has to do with freedom of speech or cryptography, I think you'll agree. Also, since they're a non-profit organization, your donation is tax deductible. Reduce your taxes while supporting strong crypto and electronic privacy. What a deal...

The Future of Private Idaho

Unfortunately, different projects and other directions are reducing the amount of time I can devote to Private Idaho, and version 2.8b3 will be my last official release. I'd still like PI to continue to evolve though. So, in an effort to see this happen, I'm releasing the entire set of Visual Basic sources. My hope is some talented, like-minded developer(s) can take PI beyond what it is today.

Before you download the sources, a small amount of fine print:

• First, there are no cryptographic algorithms within the Private Idaho source code (there never were, for export restriction reasons).
• I'm now licensing the source code and program under the Free Software Foundation's GNU General Public License. A copy of the license is included with the sources and EXE. If you plan on modifying or redistributing Private Idaho, please pay attention to the terms of the "copyleft" license agreement.
• The source code is unsupported. Because of time constraints, don't expect replies to programming questions.
• Much of the Internet-related code (sending and receiving e-mail) is based on calls to the IP*Works set of VBXs, which I licensed from a company called devSoft. When you build and run the Visual Basic sources, if you don't have a developer's license, a dialog box will appear when each of the VBXs is called for the first time. This is annoying, but doesn't impact PI's functionality. While the VBXs and OCXs are reasonably priced, they may be out of the price range for some developers. If you're interested in enhancing Private Idaho for public use, let me know. I'm willing to compile final release versions with my licensed VBXs and OCXs (for a 32-bit version).
• The current code base is in Visual Basic 3.0 (but is easily compiled under VB 4.0 or 5.0). The reason I kept developing under VB 3.0, was I felt it produced more efficient 16-bit code than the later versions (which tend to produce bloated code oriented toward Win95). Why VB in the first place? Originally PI was designed to be an internal tool with limited distribution. And I wanted a quick and dirty, fast development environment. At one point I was going to port everything to C, but realized there was too much legacy code, and it was easier just to continue using VB for updates.
• Finally, don't expect fully commented, perfectly structured, clean code, that can easily be localized. PI started out as a personal tool, and was progressively built on, piece by piece. There are many kludges and hacks. If I had any idea I was ever going to share the code with anyone, I would have used better programming practices. Oh well...