Michael Bienia wrote:
> Hello,
>
> does signing with the OpenPGP card only work with SHA1 as digest-algo?
>
> With SHA1 and RIPEMD160 gpg asks for the PIN but only SHA1 generates a
> working signature. Trying RIPEMD160 I get:
> | gpg: checking created signature failed: bad signature
> | gpg: sign
Hello,
does signing with the OpenPGP card only work with SHA1 as digest-algo?
With SHA1 and RIPEMD160 gpg asks for the PIN but only SHA1 generates a
working signature. Trying RIPEMD160 I get:
| gpg: checking created signature failed: bad signature
| gpg: signing failed: bad signature
| gpg: signi
Hi folks,
I need help to test the interoperability of my custom PGP app with other
PGP apps. One example is that I like to test my app with a PGP Universal
Server user. I'd be interested in testing with other 'not-for-free' PGP
products too. Is anybody available for a quick test? If so, p
On Mon, Mar 13, 2006 at 07:58:20AM -0500, Atom Smasher wrote:
> On Mon, 13 Mar 2006, Neil Williams wrote:
>
> >Werner et al. :
> >Maybe it's time that --send-key checks if the key to be sent has a
> >secret key in the secret keyring and if it does, prompts the user about
> >a revocation certific
Jeremiah Foster wrote:
> On Tue, 2006-03-07 at 19:35 -0500, Atom Smasher wrote:
>
>>On Tue, 7 Mar 2006, Jeremiah Foster wrote:
>>
>
>>if you have any doubts about doing it right, or if you're having a bad
>>day, backup the keyring before trying to delete anything from it.
>>
>>if no one else ha
On Mon, 13 Mar 2006, Neil Williams wrote:
Werner et al. :
Maybe it's time that --send-key checks if the key to be sent has a
secret key in the secret keyring and if it does, prompts the user about
a revocation certificate BEFORE allowing the key to be sent?
==
how many noobs
On Wednesday 08 March 2006 6:06 pm, Jeremiah Foster wrote:
> > If even the long key IDs would be equal - that should be even posted to
> > the list because it is an rarety - you'd have to use the fingerprint of
> > the key as name (if even those would be equal,.. this would be nearly a
> > sensatio
On Wednesday 08 March 2006 5:15 pm, Jeremiah Foster wrote:
> >
> > you can remove any public key from your keyring with:
> > gpg --delete-key {key-id}
>
> This prompts for the secret key id, which I do not have.
Same as the public key ID for that secret key. It's only the ID, not the key,
tha
On Tue, 2006-03-07 at 19:35 -0500, Atom Smasher wrote:
> On Tue, 7 Mar 2006, Jeremiah Foster wrote:
>
> > I overwrote the partition upon which my private key was stored. To
> > confuse matters I generated a new secret / public key pair on the same
> > machine and even imported my old public key,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Have any of you found an easy way to integrate GPG with Novell
GroupWise's Win client? There is an old project floating around which
worked with PGP and former versions of GW, but I can't find anything
recent. My institution uses GroupWoes for t
On Wed, 2006-03-08 at 18:42 +0100, Christoph Anton Mitterer wrote:
> Jeremiah Foster wrote:
>
> >Hey Chris,
> >
> >Yeah I saw that from the man page and it did not help. Specifically
> >because the names are identical and when you issue --delete-key name you
> >get prompted to specify the secret
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joerg Schmitz-Linneweber wrote:
> Hi Remco!
>
> Am Mittwoch, 8. März 2006 19:47 schrieb Remco Post:
>
>>...
>>I've started gpg-agent with:
>>
>>/usr/local/bin/gpg-agent --use-standard-socket --pinentry-program
>>/usr/bin/pinentry-gtk-2 --default-cach
Hi Remco!
Am Mittwoch, 8. März 2006 19:47 schrieb Remco Post:
> ...
> I've started gpg-agent with:
>
> /usr/local/bin/gpg-agent --use-standard-socket --pinentry-program
> /usr/bin/pinentry-gtk-2 --default-cache-ttl 1800 --default-cache-ttl-ssh
> 900 --enable-ssh-support --write-env-file $HOME/.gpg
13 matches
Mail list logo
