Some PC mail agents (notably Eudora) will decrypt the PGP message embedded within the message text. In that case, you can simply embed the [value mv_credit_card_info] call right in the message and be done with it. If your mailer will not decrypt on the fly, the best way to read the credit card number is to set up MIME encoding of the order email. To do this, find the order report you are using. In the standard demos it is pages/ord/report.html or etc/report.

PGP is excellent software, but it requires that all parties purchase and install supported software, generate their encryption keys, and then exchange those keys in a secure way.

To get PGP/GPG working, you must first install GnuPG. If you are using Apple Mac OS X, you can download a dmg here (click on GNU Privacy Guard 1.0.7r2 or 1.2.3). Once you've installed and configured GnuPG (generated your keys, etc.), you can download the PGP bundle for GNUMail.app/Mac OS X here. Mount the image and copy the PGP.bundle to your ~/Library/GNUMail/ directory. Restart GNUMail.app and everything should be fine. Note that those instructions currently only work under OS X.

Encryption garbles your data by using irreversible mathematical functions. It is simply the encoding of data so that it cannot be read by anyone who does not know the password that decodes it.

AVIA! supports RSA encryption. PGP version 5.0 should visit the PGP(tm)FAQ page. We do not currently support DSS/Diffie-Hellman encryption keys. For more information on PGP and other Security issues visit our Security page.

MuteMail supplements well with PGP or S/MIME encryption. Even if you encrypt email messages with PGP or S/MIME the message headers still remain open. "To:", "From:", "Subject:", etc. fields may disclose your identity and contain confidential information. Supplementing your encryption software MuteMail will transfer your messages through SSL encrypted tunnel for better email security. All parts of the message will be protected from interception.

On the one hand, because the transferred data is accessible in the Whois database anyway. On the other hand, because encryption is performed using the recipient's public key (here: nic.at) and therefore cannot be used for authentification.

Bulk encryption of data. Session keys are encrypted with the public key algorithm, and then the bulk of data is encrypted with a conventional block cipher. This is done for reasons of security and speed. Encrypting the keys stored in the private keyring. This keyring holds the private decryption key(s) and it is imperative that this file is encrypted in a "secure" manner. It is interesting to note that the whole of private keyring is not encrypted - but only the actual private key data.

Pretty Good Privacy? (PGP?) is a powerful cryptographic tool that provides privacy and strong authentication for users. As the de facto standard for data protection with over six million users, PGP enables you to store data and exchange messages securely. You can learn more about PGP technology at www.pgp.com and http://web.mit.edu/network/pgp.html. You can download PGP freeware without cost for personal, noncommercial use at http://web.mit.edu/network/pgp.html.

Passwords within most programs (Word, Excel, Access etc.) can be broken by mere novices without any computing knowledge. Such password breaking tools are easily available on the Worldwide Web, for as little as $5.95, or sometimes even for free! On the other hand, a file that is encrypted with a strong encryption algorithm, for example Blowfish 128 bit that Cryptainer™ LE uses, is statistically impregnable against brute force attacks.

Webtownusa.com supports RSA encryption. We do not currently support DSS/Diffie-Hellman encryption keys. For more information on PGP(tm).

The SDK includes the API, the documentation of the functions, graphics that illustrate the mechanisms applied by the API. The SDK also provides two sample projects (each action is commented) which allow you to get started easily, or create a custom application ???on top' of the sample.