Hello all I am getting a encrypted file (.pgp) and a key which i have to use to decrypt that file. I couldn't understand where to put the key on my unix box so that decryption happens. What version is it? Try to enable updates in the gt menu and restart gt. It should then ask you to update if you have an older version. You only need to put the openGhosttown to a toolbar, shortcut or quadmenu.
Pbkdf2-simple-cryptA simple encrypt/decrypt library that uses PBKDF2 to derive a key from a password (while generating a securely-random salt),encrypt using aes-256-cbc and return a string. That string includes the salt, the iv, an HMAC (hmac-sha1, which is fineas a mac), and the cipher text. The upshot of all this is you can simply encrypt and decrypt simple strings and we'll workout validity checking, etc.
I really tried to find another module that did this simple thing properly but could not. If thereis one, file an issue; if there's an issue with mine I promise to fix it.A simple example of encrypting and decrypting some text.
Let's say I have daily files that need to be encrypted using PGP (and then emailed) and I want to automate this task. I would be using Windows PowerShell to manipulate the files (examine date/times etc), but how can I automate the PGP part?I am using the PGP software manually, but I do not see any command line options.
I do see a command line software from the same place (Symantec) but for $3000 which I can't do.I found GnuPG, but (according to GnuPG's FAQ) PGP cannot decrypt GnuPG files if using v 2.x or if using v 5.x then PGP has to use more options. The receiving users are not be willing to make things more complex with extra options required.In short, I am looking for a command line PGP for Windows. The incompatibility is only for v2.x of PGP. For v5.x, the GPG (not PGP as you state) needs to have.If the problem with PGP 2.x is truly an issue, then you will probably have to shell out for the PGP command-line version. Note that and PGP v2 was in 1992-ish, so unless you are dealing with recipients that do not upgrade, you will probably have good coverage. Import your key and others:gpg -v -import c:pgpmy-pub-and-priv-pgp-key.asc Import each recipient keygpg -v -import c:pgppubrecipient1.asc.gpg -v -import c:pgppubrecipientN.ascFor some reason the command-line options are really hard to find in the locally installed Windows manual;.Now use -batch for batch mode, -passphrase-file to have your private key unlocking phrase read from the given file instead of from the keyboard via the gpg-agent., and always trust the recipient keys.
If you don't need to have the output signed, then obviously you won't need to use or unlock your private key. Encrypt (-e) and sign (-s) a filegpg -v -always-trust -batch -passphrase-file mypassphrasefile -se -rrecipient1 -r recipient2.r recipientN -o output-file file-to-encryptFiles should be able to be decrypted and verified with PGP by the recipients.I don't think I have to say what kind of potentially bad idea it is to store your private key passphrase in a cleartext file. Note that on Windows, the gpg-agent will read your private key from the keyboard and cache it. The time period it caches it for can be set in the gpg-agent.conf file, though I've not tried this (; the gpg-agent.conf resides in your home dir which is set using the GNUPGHOME env var or by setting the HKCUSoftwareGNUGnuPG:HomeDir string variable).