Turbo PGP FAQ
Turbo PGP command line software

Enables PGP encryption automation in data exchange workflow

What are the default symmetric cipher, compression, and hash algorithms TurboPGP uses?

OpenPGP allows a Transferable Public Key (i.e. the public key file) to specify the key owner's preferred cipher, compression, and signature hash algorithms. When signing or encrypting, TurboPGP uses the preferred algorithms specified in the public key in context. If any of these options are missing, TurboPGP uses its built-in defaults:

  • Cipher: AES-256
  • Hash: SHA-256
  • Compression: zlib

What platforms can TurboPGP run on?

TurboPGP can run natively on Windows, Linux, Unix, and macOS.

Where are the public keys and secret keys stored?

Public and secret keys are stored in keyring files, i.e., "pubring.tpg" and "secring.tpg" respectively. These files are located in ~/.tbpgp folder on Linux, Unix and macOS (where "~" represents the user's home folder), and c:/userdata/user/appdata/turbopgp on Windows.

What is the default extension of an encrypted file?

TurboPGP uses .pgp as the default extension of the encrypted output filename. With the --output option, the user can specify a different output filename with a different file extension.

What public key algorithms does TurboPGP support?

RSA, DSA, and ECDSA are currently supported for digital signatures. RSA, EL Gamal, and ECDH are supported for the encryption of session keys.

Can TurboPGP use keys from other OpenPGP software?

TurboPGP can import an OpenPGP public or secret key from any OpenPGP software, like GnuPG, as long as it conforms to the OpenPGP standard.

What does 'per 4-CPU' in pricing mean?

TurboPGP is licensed on the number of CPUs, counting one core as one 'CPU'. For example, you need to purchase an 8-CPU license if you plan to run TurboPGP on a server with eight single-core CPUs or four dual-core CPUs.