I'm currently reading through the doc. These people are clueless.
It been proved over and over that changing passwords often is bad. The
reason you ask? People write them down. Just like the people that put a
post-it on the back of a debit card with the PIN.
I was on the task force that wrote
Thanks for the help guys. I verified with my client and they did not export
the key correctly from PGP. All is well now.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
On Tue, Jan 02, 2007 at 05:09:59PM -0500, James Platt wrote:
> I'm writing some documentation for a particular application I support
> that uses GPG as a back end for signing documents. This particular
> implementation is subject to regulation from the Connecticut
> Department of Social Serv
On 1/2/07, John Rowan <[EMAIL PROTECTED]> wrote:
> I need to import public and private keys created by PGP 8.0. GnuPG allows
> me to import the PGP keys, but it imports all of them as public keys. I
> tried to run > gpg --import --allow-secret-key-import " ", but it
> still imported the PGP priv
I'm writing some documentation for a particular application I support
that uses GPG as a back end for signing documents. This particular
implementation is subject to regulation from the Connecticut
Department of Social Services (link to the regulations below). While
I am confident that my
On Tuesday 02 January 2007 12:11 pm, Doug Barton wrote:
> Robert Smits wrote:
> > No, it only seems to happen to me. That is, If I send a message to
> > someone else it's normal and the sig is good. But if I send a message to
> > myself, or to a mailing list and I then receive it myself, the sig is
Hello,
I am trying to perform a digital signature with a S-Trust (card issuer
behind some german banks, "Sparkassen") signature card. This is a
qualified signature card according to german signature law. Technically,
it's a SECCOS card from Giesecke & Devrient. The file system complies to
the germ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
John Rowan wrote:
> I need to import public and private keys created by PGP 8.0. GnuPG allows
> me to import the PGP keys, but it imports all of them as public keys. I
> tried to run > gpg --import --allow-secret-key-import " ", but it
> still imp
Robert Smits wrote:
> No, it only seems to happen to me. That is, If I send a message to someone
> else it's normal and the sig is good. But if I send a message to myself, or
> to a mailing list and I then receive it myself, the sig is marked bad.
This is starting to sound like something you mi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Rowan wrote the following on 1/2/07 5:31 AM:
> I need to import public and private keys created by PGP 8.0. GnuPG allows
> me to import the PGP keys, but it imports all of them as public keys. I
> tried to run > gpg --import --allow-secret-key-i
On Tue, Jan 02, 2007 at 04:31:45AM -0600, John Rowan wrote:
> I need to import public and private keys created by PGP 8.0. GnuPG allows
> me to import the PGP keys, but it imports all of them as public keys. I
> tried to run > gpg --import --allow-secret-key-import " ", but it
> still imported t
I need to import public and private keys created by PGP 8.0. GnuPG allows
me to import the PGP keys, but it imports all of them as public keys. I
tried to run > gpg --import --allow-secret-key-import " ", but it
still imported the PGP private key as a public key in GnuPG. Am I missing
something
Hi,
engage schrieb:
> I wasn't able to encrypt to someone even though their key is on my
> keyring. I get a message that no valid and trusted key could be found for
> the recipient.
Maybe you try to write to another email address of the same person that's
not listed in the key?
Best wishes
Micha
Hi,
I just discovered gpg-agent and it's useful to type my passphrase less
often.
Without gpg-agent, when gpg prompts me for a passphrase, it does not
display the number of characters I type. But when I enter my passphrase
in gpg-agent, a star is displayed for every letter I type (I use
pinent
14 matches
Mail list logo
