OS/2 Shareware BBS: 3 Comm

home *** CD-ROM | disk | FTP | other *** search

/ OS/2 Shareware BBS: 3 Comm / 03-Comm.zip / gopgp120.zip / GOPGP.DOC < prev next >

Wrap

Text File | 1998-10-05 | 19KB | 375 lines

██████╗ ██████╗ ██████╗ ██████╗ ██████╗ ██╔════╝ ██╔═══██╗ ██╔══██╗ ██╔════╝ ██╔══██╗ ██║ ███╗ ██║ ██║ ██████╔╝ ██║ ███╗ ██████╔╝ ██║ ██║ ██║ ██║ ██╔═══╝ ██║ ██║ ██╔═══╝ ╚██████╔╝ ╚██████╔╝ ██║ ╚██████╔╝ ██║ ╚═════╝ ╚═════╝ ╚═╝ ╚═════╝ ╚═╝ Version 1.20 `'`'`'`'`'`' What is it? ~~~~~~~~~~~ GOPGP is a PGP Front-End (And, optionally, a full-featured tagline manager) for DOS or OS/2 that makes using PGP with your off-line mail reader a LOT easier! I wrote this because I couldn't find any PGP Front- ends for OS/2, and I wanted some specific features and ease of use that other similar programs didn't have, I made it freeware because PGP itself is freeware, and I don't think it would be right to make money from someone else's work. All I ask in the way of "registrations" is for you to send me over an E-Mail message telling me you're using the program, just so I know that all this work wasn't in vain. Legal Stuff: ~~~~~~~~~~~~ The author assumes no liability for damages resulting from the use of this software, even if the damage results from defects in this software, and makes no representations concerning the merchantability of this software or its suitability for any specific purpose. It is provided "as is" without express or implied warranty of any kind. Because certain actions may delete files or render them unrecoverable, the author assumes no responsibility for the loss or modification of any data. "PGP", "Pretty Good Privacy", "Phil's Pretty Good Software", and the "Pretty Good" label for computer software and hardware products are all trademarks of Philip R. Zimmermann. PGP is (c) Copyright Philip R. Zimmermann, 1990-1994. All rights reserved. The PGP User's Guide is also copyright Philip Zimmermann, 1990-1994. All rights reserved. These rights include but are not limited to any foreign language translations of the manual or the software, and all derivative works of both. System Requirements: ~~~~~~~~~~~~~~~~~~~~ DOS Version (GOPGP.EXE) - It runs great here under DOS on a 386-SX with 4 megs of RAM, so it should run on almost anything. OS/2 Version (GOPGP2.EXE) - Warp 3 or higher. If you can run Warp 3 you shouldn't have any problems. (If you would like a 16-bit version, E-Mail me and I'll see what I can do) Win32 Version (GOPGPW.EXE) - Windows'95/98/NT. If your system can run Windows, you shouldn't have any problems running GOPGP. How To Use It: ~~~~~~~~~~~~~~ Simple! Couldn't be easier! Just unzip to any directory (Since you're reading this, I'll assume to already did that, so I won't bore you by explaining HOW to unzip a file). IMPORTANT! If you are upgrading from version 1.00, you *MUST* delete your old GOPGP.CFG, as the format of the config file has changed, configuration is now internal instead of a text file. Next, call it from your mail reader and you will be prompted to create a new config file. Here is an explanation of all of the config options: Your Username (The name used in your PGP key): This will be used in the PGP command-lines to specify the name you use to decrypt/sign/etc.. Path to where PGP is stored: This is the path to your PGP Directory, You only need the path (NOT The filename!) For example "D:\MY\STUFF\PGP\" (Without the quotes). The Path And Name Of Your External Editor: This can be any program that edits text-files (Like you didn't know that already! :> ) Just enter the path/name of your editor of choice (NOTE! OS/2 users should refer to the "Restrictions" section) "@F" will be replaced with the message filename. For example: "C:\UTIL\EDITOR.EXE @F /F" Path/Filename Of Default Signature File: This file (Text) will be inserted into the bottom of every message you write. If you press ENTER at this prompt, signature support will be disabled. Append PID, TEAR, BOTH, or NONE To Messages?: Just like it says, if you set this to PID, a PID line will be added to the top of your message, if set to TEAR, a tearline will be appended to the end of your messages, if you set this to BOTH, both will be added, and if you set this to NONE, neither will be added. Path/Name Of External File Viewer: (IE: C:\DOS\VIEW.COM @F) Put the name and command-line switches to load your external viewer, "@F" will be replaced with the message filename. If you press ENTER on this line, the internal file viewer will be used instead. Auto-Detect/Decrypt Encrypted Messages? (Y/n): If you set this option to Yes, GOPGP will automatically detect whether or not the message is encrypted. If it is encrypted, you will be prompted to automagically decrypt it, Yes or No. (Note: When automatically decrypting messages, you do not need to first remove quote chars ("SH> " for example) from the beginning of each line, as GOPGP does this automatically) Path/Filename Of Your Tagline File: If you wish to add taglines to the end of your message, define the path/filename of an ASCII text file which contains single-line, 75 character or less "taglines". If you press ENTER on this line, Tagline support will be disabled. Path/Name Of Your After Edit Utility: This is the command-line and parameters of a utility to be executed after you edit each message. This could be a spell-checker, an external tagline manager, etc.. (IE: C:\SS\SS.EXE @F) Put the name and command-line switches to load your external utility, "@F" will be replaced with the message filename. Pressing ENTER on this line will disable this feature. Path Where Your Tagfile/Signature Files Are Stored: This is the directory where you store your tagline files and signature files. This is necessary for when you select "Change Tagfile" or "Change Signature" from the tagline selection menu. Tagline files must be named *.TAG and signature files must be named *.SIG. If you press ENTER on this line, when changing tag/sig files you will simply be prompted to enter a filename. Spell Checker: Unlike the afteredit utility (Which is run after editing every message) the spell checker is only run when you ask it to. As with all other external utilities, @F will be replaced with the message filename. Pressing ENTER on this line disables this feature. Command-Line: ~~~~~~~~~~~~~ Usage: GOPGP(2/W).EXE <name of message file> [switch] <name of message file> = Mandatory [switch] = Optional Switches: /E - Jump Into Message Editor First /S - Sign Message And Exit /D - Decrypt Message And Exit /A - Encrypt & Sign Message And Exit /N - Encrypt Message And Exit /C<filename> - Use <filename> As Config File Use with Bluewave Off-Line Mail Reader: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I'm not sure about other versions of Bluewave, but I run Bluewave 2.30/DOS and it runs great here. To set it up is simplicity in itself. You have to have some kind of "Swapping" enabled (XMS/EMS/DISK) to free up enough memory for PGP, your editor, etc.. (Check the Global/Memory Swapping Options/Swap for Msg Editor and be sure it's set to "Yes"). Then go to the "External" menu and change the "Message Editor Cmd" to "D:\PATH\TO\GOPGP\GOPGP(2/W).EXE @F" along with any other command-line switches you would like to use. I recommend using the "/E" switch, so you don't have to look at my menus every time you edit the message. That command line would look something like this; "D:\PATH\TO\GOPGP\GOPGP(2/W).EXE @F /E". If you are using Gopgp's tagline support, you'll want to go to Preferences/Default Preferences/Tagline Behavior and set "Tagline Selection Type" to "No Tags". Also, if you're using GOPGP's internal signature support, you'll want to go to Preferences/Default Preferences/File And String Preferences and erase the "Signature File Name" field (So that it's left blank). Just so that you don't end up with two signatures/taglines on your messages. Use with MsgEd: ~~~~~~~~~~~~~~~ For use with the MsgEd Sysop Mail Reader, you *MUST* have ATLEAST version 4.20 for GOPGP to work correctly, as earlier versions didn't swap out of memory properly so PGP didn't have enough memory to function, resulting in horrid problems I won't go into here. The OS/2 and Win32 versions of MsgEd shouldn't have this problem, and I know that MsgEd/2 TE 04 and 05 work properly. The set-up for MsgEd is even more simple than Bluewave's set-up, just add the following line to your MSGED.CFG file: Editor GOPGP.EXE /E You don't have to worry about passing the filename, MsgEd will pass it at the end of the command-line when calling your editor. Also, just to be safe, I've found that adding these lines; Switch Hardquote On Switch ExtFormat Off will prevent MsgEd from re-formatting the quote (and your PGP mail in the process) and allows PGP to decrypt messages properly. Use With Golded: ~~~~~~~~~~~~~~~~ For use with GoldEd, you must add atleast one line to the config file, you could also add any of several other lines to make your life easier, but those are up to you. The line you will need looks something like this; EDITOR D:\PATH\TO\GOPGP\GOPGP.EXE @FILE /E The "/E" just makes it jump directly into the message editor (VERY convenient) which is optional. If you would like to be able to use GOPGP's macro functions but want to use your internal editor for certain messages, you can add the following to your config file also; EXTERNOPTIONS -nokeepctrl -wipe -PauseOnError EXTERNUTIL 1 D:\PATH\TO\GOPGP\GOPGP.EXE @TMPFILE /S EXTERNUTIL 2 D:\PATH\TO\GOPGP\GOPGP.EXE @TMPFILE /N EXTERNUTIL 3 D:\PATH\TO\GOPGP\GOPGP.EXE @TMPFILE /A EXTERNUTIL 4 D:\PATH\TO\GOPGP\GOPGP.EXE @TMPFILE /D EXTERNUTIL 5 D:\PATH\TO\GOPGP\GOPGP.EXE @FILE EDITSAVEUTIL 1 "S PGP Sign the msg" EDITSAVEUTIL 2 "E PGP Encrypt the msg" EDITSAVEUTIL 3 "T PGP EncrypT & Sign the msg" EDITSAVEUTIL 5 "P GOPGP" Also, add the following to GOLDKEYS.CFG: F11 ExternUtil02 ; Press F11 to Encrypt a message F12 ExternUtil04 ; Press F12 to decrypt the current message. With this set-up, the first difference you will notice is when you enter a new message. On the menu that comes up, you will see Internal Editor AND External Editor, if you select External Editor, you will be brought to GOPGP, and into your message editor (If you use the "/E" switch) With the latter portions of the config file I've included, you will have several new options on your "Save Message" menu. You will now see "Sign Message", "Encrypt Message", "Encrypt & Sign Message" and "GOPGP". As for the portions to add to the GOLDKEYS.CFG, as you can see by the comments above, when you are viewing an encrypted message, you simply press F12 to decrypt it, and if you are viewing a 'normal' message, you can simply press F11 to encrypt the message. Use With Other Programs: ~~~~~~~~~~~~~~~~~~~~~~~~ If you use a program for your mail that isn't listed in these DOC's, please, by all means, send me a detailed set of setup instructions (IE: How you got it to work) at my E-Mail address (found in "Contacting Me") so that I may include it in the DOC's for the next version, and maybe make someone's life a lot easier. After all, I can't know how to set this up for programs I don't run, right? About the only thing I can suggest you do to run this with another program is, make sure your program isn't reformating the message at any time, and use some common sense when it comes to the command-line switches. I don't see any reason why this can't run under any program that allows an external editor. Internal File Viewer: ~~~~~~~~~~~~~~~~~~~~~ The internal file viewer is quite simple to use, when you start the internal viewer, there are several keystrokes which can be used to move around, and to adopt taglines. The following keys can be used to move around, and are very straightforward: Up, Down, PageUp, PageDown, Home, and End. To adopt a tagline from the screen to the end of your defined tagline file, press Alt-A. To quit the viewer, simply press Esc. Signatures: ~~~~~~~~~~~ A signature file is a plain ASCII text file that will be added to the end of your messages (unless you have signatures disabled). If you would like, you can put one or more of three macro's in your signature file. If you put @T@ in your signature file, it will be replaced with the current time (HH:MM:SS), if you put @D@ in your signature file, it will be replaced with the current date (MM/DD/YYYY), and if you put @DOW@ in your signature, it will be replaced with the day of the week (Sunday, Monday, etc..). For example: "@DOW@, @D@" would expand to: "Sunday, 12/21/1997", and: "Written @DOW@, @D@ at @T@" would expand to: "Written Sunday, 12/21/1997 at 12:30:45" Key Management: ~~~~~~~~~~~~~~~ The key management menu harnessess most of PGP's key management features, such as; adopting public keys from the message, appending your public key to the message, viewing your public keyring, removing keys from your public keyring, editing your secret key (passphrase, adding usernames, or editing the trust parameters on your public key) generating a key pair, and revoking your key. NOTE!! Revoking your key is fairly serious, because once it's been revoked, if people send you encrypted mail with that key, you will not be able to decrypt it. So to revoke your key, you must type "IAGREE" (without the quotes) to confirm that you do infact wish to permanently revoke your key. Tagline Selection: ~~~~~~~~~~~~~~~~~~ Here is a brief explanation of all the items on the tagline selection menu: Y - Use This Tagline Pressing Y or ENTER will accept the current options. IE: The tagline, signature, etc.. N - Select New Tagline Select a new random tagline from the current tagfile L - List Ten Selects ten random taglines and prompts you to select one of them, list another ten, or abort (keep current tag). Q - Quit, No Tag or Sig Pressing Q or ESC aborts, and adds no signature or tagline. C - Change Tagfile If you specified a valid path for the "Path where tag/sigfiles are stored" this will bring up a list of all files named *.TAG within that path. (Only the first 26 tagfiles found will be listed) Otherwise it will bring up a prompt asking you to type in the name of the new tagline file. S - Change Sigfile As above, if the path for "Path where tag/sigfiles are stored" contains any files named *.SIG it will bring up a list of these signatures and prompt you for your selection (Only the first 10 sigfiles found will be listed). Otherwise it will prompt you for the path and filename of the new sigfile. T - What To Add This simply selects whether you would like to add TAG only, SIG only, or BOTH. (Defaults to BOTH) R - Run Spell-Checker If you have the spell checker option set, this item will run it. Unlike the "After Edit" utility (run after EVERY message) this will only be run when you press 'R' from this menu. UU Encoding/Decoding: ~~~~~~~~~~~~~~~~~~~~~ Support has just been added for UU Encoding/Decoding files. When you decode a file from your message, GOPGP will be able to UUDecode the file ONLY if there are A) No quote characters at the beginning of the lines, or B) The quote characters are standard (IE: A ">" characters followed by a space, then the message text. This could also include initials in front of it, like " SH> ", but there *MUST* be a ">" symbol followed by a space!). Also - Since I'm not psychic, to UUDecode a file, it must be in ONE message (With NO blank lines between the "Begin 644 <filename>" and the word "end"). If you do receive a UUEncoded file that gets split into several messages, you can simply use a text editor to combine the UUENcoded messages into one text file, then run GOPGP with the command line "GOPGP <textfilename>" and decode the message from there. Also, please keep in mind that when UUEncoding files into your message, it will all be put into one single message, so UUEncoding a 3 MEG file would make for one LONG message. Restrictions: ~~~~~~~~~~~~~ If you are using the OS/2 version, you *MUST* also use the OS/2 version of PGP and an OS/2 specific text editor. But why bother using DOS apps under OS/2 if you don't have to? If you don't want to use the OS/2 version of PGP, you COULD run the DOS version of GOPGP under OS/2, with a DOS text editor and the DOS version of PGP. I'll look for a way to get around this in future versions, providing I get enough user-feedback in support of it. Version Numbering: ~~~~~~~~~~~~~~~~~~ Just incase anyone is wondering how I number each version, the version scheme is very simple. When I first started the program, I used version numbers 1.00ß1 through 1.00ß5, until the first release which was version 1.00. The version scheme I use now goes as follows - Public releases will be numbered in increments of one tenth from the previous release (IE: 1.10, 1.20, 1.30, etc..) and the beta versions will be incremented one hundredth from the last public release (IE: 1.02, 1.03, etc..) Error Messages: ~~~~~~~~~~~~~~~ If the program halts with an error message, it will also create a file in the program directory called ERROR.LOG. If you do see this log file, please send it to the me immediately, as it will contain enough information for me to find, and possibly solve, the problem. Contacting Me: ~~~~~~~~~~~~~~ If you want to get ahold of me, for bug reports, or for features you would like to see added/changed, or just to drop me a line to tell me you are using this program (and like it), you can send me Internet E-Mail at blackdeath@tinys.oix.com (no file-attaches) or s_honsberger@usa.net (file attaches allowed) or you could visit me at my web page at: http://tinys.oix.com/blackdeath and I'll do my best to help you out. I've included my PGP public key in this archive in the file STEWART.KEY, if you wish to encrypt your message to me. Credits: ~~~~~~~~ Just want to give thanks to Shawn 'Tiny' Highfield for Beta testing for me all this time.