Re: dirmngr cygwin resolv.conf

2018-07-02 Thread john doe
On 7/2/2018 8:48 AM, Werner Koch wrote: On Sat, 30 Jun 2018 21:26, johndoe65...@mail.com said: How can I force dirmngr to use port "9150"? So Tor ports are fixed. As Niibe-san already explained Dirmngr will first try port 9050 and if it is not able to connect (ECONNREFUSED) it will try port

Re: Generating NIST/Brainpool subkeys with GPGME

2018-07-02 Thread Jacob Adams
On 07/02/2018 02:37 AM, Werner Koch wrote: > On Fri, 29 Jun 2018 22:07, tookm...@gmail.com said: >> It appears that one cannot currently generate NIST or Brainpool subkeys >> with GPGME. Using GPG itself works fine with --expert, so am I missing >> an option or is this simply not possible yet? >

Re: Choice of ECC curve on usb token

2018-07-02 Thread Wiktor Kwapisiewicz via Gnupg-users
Hi Damien, I was referring to the discussion around RSA vs. ECC in https://crypto.stackexchange.com/questions/60392/choice-of-ecc-curve-on-usb-token/60394#60394 I read several texts of people preferring RSA over ECC. That's an excellent answer, thanks for posting this! I've came up with the

Re: Choice of ECC curve on usb token

2018-07-02 Thread Damien Cassou
Phil Pennock writes: > On 2018-06-29 at 18:07 +0200, Damien Cassou wrote: >> I'm not sure I want ECC after reading this: >> https://crypto.stackexchange.com/a/60394/60027 > > Curve25519 is not NIST ECC. It is ECC. I was referring to the discussion around RSA vs. ECC in

Re: Choice of ECC curve on usb token

2018-07-02 Thread Werner Koch
On Fri, 29 Jun 2018 18:07, dam...@cassou.me said: > Moreover, Nitrokey Storage only supports NIST and Brainpool, nothing > else. That is because the Nitrokey token includes a Zeitcontrol card which only implements the government approved curves. If that ever changes we can close the feature

Re: dirmngr cygwin resolv.conf

2018-07-02 Thread Werner Koch
On Sat, 30 Jun 2018 21:26, johndoe65...@mail.com said: > How can I force dirmngr to use port "9150"? So Tor ports are fixed. As Niibe-san already explained Dirmngr will first try port 9050 and if it is not able to connect (ECONNREFUSED) it will try port 9150. This is implemented for Dirmngr in

Re: gpg2 --refresh-keys does not talk to dirmngr?

2018-07-02 Thread Werner Koch
On Fri, 29 Jun 2018 16:12, gnupg-users@gnupg.org said: > I have set up a local proxy server with a squid/privoxy/TOR chain and > set it up in dirmngr.conf. Now, after deleting the keyserver line from > gpg.conf, I found out that gpg2 seems not to talk to dirmngr when using > gpg2 --refresh keys.