[no subject]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone. The last gpg-agent supports ECDSA and putty's pageant. But, does it support ECDSA for putty/pageant ? Regards. -BEGIN PGP SIGNATURE- Version: APG v1.0.8 iQI7BAEBCAAlBQJSJbADHhxNdXN0cnVtIDxNdXN0cnVtQE11c3RydW0ubmV0PgAK CRBMuv2

Gpg-agent ECDSA and pageant

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone. The last gpg-agent supports ECDSA and putty's pageant. But, does it support ECDSA for putty/pageant ? Regards. Ps: oups, sorry for my last message without any subject, bad clicking... -BEGIN PGP SIGNATURE- Version: APG v1.0

GnuPG 2.1 pinentry copy/paste on windows system

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 If you need to be able to past your 'very strong passphrase' (may be from keepass) you can use the old pinentry provided with gpg4win 2.2, without install it. Open the installer with 7z and copy all the dll and pinentry exec onto a new ditectory.

GnuPG 2.1.0 Merging secret key

Hi all, I'm merging one of my 'old' sub-key into another key-pair. It kept the same keygrip but got a new ID/fingerprint. How can I use that new subkey to decrypt something encrypted to my 'old' subkey ? Regards ___ Gnupg-users mailing list Gnupg-use

GnuPG 2.1.0 Merging secret key

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, >My guess would be the option "--try-secret-key name" where "name" might be the >subkey's new ID followed by an exclamation mark. Nope I got the error "no secret key available". I'm wondering : what is the planned usage for that feature ? -

Re: GnuPG 2.1.0 Merging secret key

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I was wondering about merging secret keys. Le 14 novembre 2014 08:58:45 CET, Werner Koch a écrit : >On Thu, 13 Nov 2014 21:00, must...@mustrum.net said: > >> I'm wondering : what is the planned usage for that feature ? > >--try-secret-keys is used

Using Smartcards without it's public key

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Can I use my openPGP smartcard to decrypt a file with a empty keyring ? Assuming the card's public keys are lost or unreachable at the time. Regards. -BEGIN PGP SIGNATURE- Version: APG v1.0.8 iQIVAwUBT1CXn0y6/YZf1YOeAQpSDg//UuBx2Ydaj

Re: Using Smartcards without it's public key

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 03/03/2012 22:14, Werner Koch a écrit : > No. Public OpenPGP keys are often pretty lare and would not fit on the card. Thus we decided not to do it at all. My usually advise is to put an URL to the public key into the URL field and then use the fe

Re: Using Smartcards without it's public key

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 04/03/2012 00:20, Todd A. Jacobs a écrit : > I *think* this is either because the key lookup is happening on the public key first, before checking for the matching secret key, or because the stubs aren't being created right in the keyrings. I am h

Re: failed to build a binary for version 2.0.19 please advise

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > On 04/07/2012 11:28 PM, ? wrote: >> Execuse me where can I find the binaries of this new version on >> a windows platform > http://files.gpg4win.org/gpg4win-2.1.0.exe > Enjoy. I gather that a new build is expected soon, but last time I

Re: Current key servers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 How can we use private IPs ? >OK, here's my list of addresses: >192.168.1.2booboo # Windows 2003 Svr[*] >192.168.1.4yogi# Slackware Linux >192.168.1.5picnic # Slackware Linux >192.168.1.18 basket # MacOS X >192.168.1.19 horse

Re: There may be more to security than password length, or even its complexity.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Http://xkcd.com/538 :-) -BEGIN PGP SIGNATURE- Version: APG v1.0.8 iQI7BAEBCgAlBQJPvPDuHhxNdXN0cnVtIDxNdXN0cnVtQE11c3RydW0ubmV0PgAK CRBMuv2GX9WDnv71EADJYr8hgWu/5yGnKgrYHhE/w+uxieCAAtIlZDvXxHKKVFGC MC1xVgeYeksvM8fNL4RPMCs5ttsi1uA0OUax6jGxUg7W

Re: Separate OpenPGP cards for master key and sub-keys

I already moved my subkeys to one cryptostick. When i tried to move the primary key (4096 RSA) to another stick i got: >gpg> keytocard >Really move the primary key? (y/N) y >Signature key : [none] >Encryption key: [none] >Authentication key: [none] >Please select where to store the key: >

Re: Separate OpenPGP cards for master key and sub-keys

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Pete Stephenson a écrit : >On Mon, Jun 3, 2013 at 11:10 AM, Mustrum wrote: >> I already moved my subkeys to one cryptostick. >> When i tried to move the primary key (4096 RSA) to another stick i >got: >> >>>

Re: Separate OpenPGP cards for master key and sub-keys

Peter Lebbing a écrit : >On 03/06/13 20:10, Mustrum wrote: >> Note that there is NO valid choice. > >Stick it in signature, that works. > >Peter. -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Peter Lebbing a écrit : On 03/06/13 20:10, Mustrum wrote: Note that the

Re: Separate OpenPGP cards for master key and sub-keys

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Le 05/06/2013 14:50, Peter Lebbing a écrit : > On 05/06/13 12:55, Mustrum wrote: >> The keytocard command displays the 3 slots, but none of them are >> listed as a valid choice. I've to choose from an empty list. > > Ah

Re: Separate OpenPGP cards for master key and sub-keys

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Le 05/06/2013 20:20, Peter Lebbing a écrit : > On 05/06/13 19:37, Mustrum wrote: >> I'm quite sur the root cause is the "certification only" capacity >> of my key: > > I'm quite sure I never had data signat

Re: Separate OpenPGP cards for master key and sub-keys

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Peter Lebbing a écrit : >On 05/06/13 22:57, Mustrum wrote: >> how can we change a key capability ? > >Hmmm. Good point. No idea :) > >If you use a hex editor to change flags, the signature will not check >out. >P