On Mon, 1 Mar 2010 22:13, ds...@jabberwocky.com said:
someone elses key. The current design effectively forces people to
manually move the valuable primary key out of the way before
clobbering it with the subkey-only copy of the key.
Another important point is that if you want to use an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Werner Koch escribió:
...
Another important point is that if you want to use an offline key you
should create that key offline and export the subkeys to the online box.
Doing this on the same box is a bit questionable. To me an offline key
is
On Tuesday 02 March 2010, Faramir wrote:
Werner Koch escribió:
...
Another important point is that if you want to use an offline key
you should create that key offline and export the subkeys to the
online box. Doing this on the same box is a bit questionable. To
me an offline key is
The Setup
I run Windows XP using GnuPG version 1.4.10.
A client and I have exchanged our keys. I successfully imported his key and
attempted to encrypt a file to send him. My command line is as follows:
gpg --passphrase mypassphrase --compress-algo 1 --cipher-algo cast5 -u
m...@myemail.com
On 3/2/2010 5:31 PM, 20 Ton Squirrel wrote:
The Setup
I run Windows XP using GnuPG version 1.4.10.
A client and I have exchanged our keys. I successfully imported his key and
attempted to encrypt a file to send him. My command line is as follows:
gpg --passphrase mypassphrase
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
20 Ton Squirrel escribió:
...
My key's ID is 1F1EA8F8 and the client's ID is 5872AF6A. I have no idea why
it would be asking for A352B4E9003B38FA.
I tried using the GUI, and in fact, the error message shows the ID of
the encryption subkey
Hello 20 !
20 Ton Squirrel andy_cr...@npd.com wrote:
The Setup
I run Windows XP using GnuPG version 1.4.10.
A client and I have exchanged our keys. I successfully imported his key and
attempted to encrypt a file to send him. My command line is as follows:
gpg --passphrase mypassphrase
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
20 Ton Squirrel escribió:
...
The Problem
When trying to decrypt or verify the encrypted file, I get the following
error:
No secret key available Keyring does not have the secret key
(0xA352B4E9003B38FA) needed to decrypt this message.
I am
Folks
The gpg --import option worked without any problems for importing the OpenPGP
public keyring. When I try to import the secret keyring, I get the following
message:
[app1 ~/.gnupg]$ gpg --import secring.skr
gpg: key B4A839CC: secret key imported
gpg: key B4A8899S: ofc not changed
gpg:
What are the ramifications of just saying yes to the prompt - update
preferences? How potentially serious is the algorithm mismatch? I'd like to
better understand exactly what is happening.
Ever since the very early days, PGP has supported a cryptographic algorithm
called IDEA. Back in
On Mar 2, 2010, at 9:18 PM, Smith, Cathy wrote:
Folks
The gpg --import option worked without any problems for importing the OpenPGP
public keyring. When I try to import the secret keyring, I get the following
message:
[app1 ~/.gnupg]$ gpg --import secring.skr
gpg: key B4A839CC:
While I understand the response. It fails to consider the persistence of
the exposed password. If it is volatile within the script issuing the
commands, then the pass-phrase has considerable value as a security measure.
---
My problem (which relates to this) I have an ODB (OpenOffice.Org)
My problem (which relates to this) I have an ODB (OpenOffice.Org) database
file which I would like encrypted. The process would be to get the
pass-phrase from the user, decrypt the file, run soffice -base, and then
re-encrypt the results with the same password.
This sounds like a use case
13 matches
Mail list logo
