The binaries are here, but look at the code.  Other components (RSA,
Blowfish, MD2/5, etc.) are in pilotSSLeay which is from the SSLeay
library.  See the copyright notice at the end, and verify local
patent, copyright, and crypto restrictions.

The original Pilot port of SSLeay is by Ian Goldberg
<ian@cypherpunks.ca> and is at http://www.isaac.cs.berkeley.edu/pilot/

I have only included a minimum set for the MUST algorithms. it is up
to you to verify it is legal for you to use more modules if you want
to add more, and portions I have ported.

The two .asc files are keyrings.  The passpharase is "testpass".
Create an address book entry for this and copy the pubkey text into
the note.  Copy the secret key text to the clipboard and use Decrypt
to set the secret key.

You can substitute your secret keyring by armoring it and replacing
-----BEGIN PGP MESSAGE----- with -----BEGIN PGP PRIVATE KEY BLOCK-----
and can change secret keys by simply copying the one you want to use
to the clipboard and using the decrypt function.

Note that no validity checking of keys is done.  I assume you will do
that on your desktop, and export only the valid public keys (using
pgpk -xa or pgp -kxa depending on version).

After extracting public keys, add them as a note in the address book.
You will need to do this for your own key as well as any others.  When
you have all your keys (or when you add or update any), select the
Build Ring entry from the menu to rebuild the internal pubring.

In this version, only the first key on the secret ring will be used
for signing.

I recommend EcoHack to speed things up.  Otherwise you may need to
increase the auto-off timer.  You will also need ClipHack or another
clipboard extender.  It takes time due to the complexity of the
mathematics, particularly with high security keys.

=========================
To (Clear)Sign text:

Copy it to the clipboard, start my app, and tap Clearsign, then tap
RUN.  You will get a popup if your secret key is passphrase protected
(which it should be).  The signed message will be placed on the
clipboard.

=========================
To Verify a signature:

Copy the entire message (from the ----BEGIN PGP SIGNED MESSAGE----- to
the -----END PGP SIGNATURE-----) to the clipboard, start PGP, tap
decrypt, and it will print a message indicating the validity of the
signature (or if the signature is bad or if no verify key exists).

=========================
Encrypting:

Copy the text to be encrypted to the clipboard.

Select which processes you want done (Signing, Compression, Encryption
(passphrase only), and Armoring - note the text clipboard can contain
binary data, but other applications might not recognize it properly,
so Armoring is recommended).  Tap Encrypt, then Run.  If you didn't
specify NonPK, a popup will appear so you can select the recipient.  A
popup will also appear for any passphrase (signing will need one, as
will passphrase encryption).  The encrypted message will then be on
the clipboard.

=========================
Dearmor/Decrypt/Decompress/etc:

Simply copy the entire message to the clipboard, bring up my app,
click Decrypt and RUN.

The literal filename will be prepended to the text, and the whole
thing placed on the clipboard.

=========================
Signing Keys

Tap signkeys and then run.  The popup will select the key to sign.
You will be asked for your passphrase if your secret key is locked (it
should be).  The resulting public key block will end up on the
clipboard.  The signature is the first userid of the first signing key
for the selected user (which may be different than the email address).

=========================

SSLeay terms:

/* Copyright (C) 1995-1997 Eric Young (eay@cryptsoft.com)
 * All rights reserved.
 *
 * This package is an SSL implementation written
 * by Eric Young (eay@cryptsoft.com).
 * The implementation was written so as to conform with Netscapes SSL.
 *
 * This library is free for commercial and non-commercial use as long as
 * the following conditions are aheared to.  The following conditions
 * apply to all code found in this distribution, be it the RC4, RSA,
 * lhash, DES, etc., code; not just the SSL code.  The SSL documentation
 * included with this distribution is covered by the same copyright terms
 * except that the holder is Tim Hudson (tjh@cryptsoft.com).
 *
 * Copyright remains Eric Young's, and as such any Copyright notices in
 * the code are not to be removed.
 * If this package is used in a product, Eric Young should be given attribution
 * as the author of the parts of the library used.
 * This can be in the form of a textual message at program startup or
 * in documentation (online or textual) provided with the package.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 * 3. All advertising materials mentioning features or use of this software
 *    must display the following acknowledgement:
 *    "This product includes cryptographic software written by
 *     Eric Young (eay@cryptsoft.com)"
 *    The word 'cryptographic' can be left out if the rouines from the library
 *    being used are not cryptographic related :-).
 * 4. If you include any Windows specific code (or a derivative thereof) from
 *    the apps directory (application code) you must include an acknowledgement:
 *    "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
 *
 * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 *
 * The licence and distribution terms for any publically available version or
 * derivative of this code cannot be changed.  i.e. this code cannot simply be
 * copied and put under another distribution licence
 * [including the GNU Public Licence.]
