Re: GnuPG modern can't genereate keys on my Windows

2015-09-07 Thread Werner Koch 
On Sun,  6 Sep 2015 10:11, dongsheng.s...@gmail.com said:

> In theory, you are right. But ALL Windows kernel object include HANDLE
> lower than 2^24.

I have seen kernel objects with a higher value.  Not necessary HANDLE,
though.

> Then if these cast is safe for 64 bit Linux, then safe for Windows too.

Nope.  Almost all 64 bit Unix systems implement the LP64 data model
where a "long" and all pointers are 64 bit.  Windows however uses LLP64
where only "long long" and pointers are 64 bit.  Further, file
descriptors on Unix are always a 32 bit "int" but on 64 bit Windows the
kernel objects resembling file descriptors are all pointers and thus 64
bit.  On 32 bit Windows pointers have the same size an "int" and thus we
can represent them using an int and convert them using atoi.

>>  2. In the summary page you state that the license is CC BY-SA.
>> However, both GCC and GnuPG are under the GPL.  You need to fix
>> that!
>>
>
> Thanks, fixed.

Thanks.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-07 Thread Werner Koch 
On Sun,  6 Sep 2015 16:29, joh...@vulcan.xs4all.nl said:

> Perhaps they accept larger files or can use more memory? I do remember

Should all be the same.  I see no practical reason for using a 64 bit
binary.  I even doubt that it will be faster because gpg does no
allocate large memory blocks.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-06 Thread Dongsheng Song 
On 2015-09-06 18:02, Peter Lebbing wrote:
> Is there any reason to provide 64-bits binaries, BTW? It's an unbiased
> question, I simply don't know. Does it provide any benefits?

Yes, when we running 64 bit Windows, use 64 bit binary is naturally requirement.

WoW64 is optional component for Windows server, for those servers without WoW64,
running 64 bit binaries is the only choice.



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-06 Thread Robert J. Hansen 
> Is there any reason to provide 64-bits binaries, BTW? It's an unbiased
> question, I simply don't know. Does it provide any benefits?

Potentially.  It allows the compiler to use x64 features such as W^X,
which relies on there being an NX bit in the page table entry.  This
wasn't part of the x86 design, but was added by AMD for the x64.  Then
Intel backported it to the Prescott architecture for the Pentium-4.  But
unless you can guarantee you'll never run on pre-Prescott chips, you
can't rely on W^X.

True, W^X is an OS-level feature and not a GnuPG feature.  But it should
work as an example of how the two instruction sets could be different in
ways important for computer security.

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-06 Thread Johan Wevers 
On 06-09-2015 12:02, Peter Lebbing wrote:

> Is there any reason to provide 64-bits binaries, BTW? It's an unbiased
> question, I simply don't know. Does it provide any benefits?

Perhaps they accept larger files or can use more memory? I do remember
once compiling the pgp 2.6.3ia sources with Visual Studio 5 long ago to
make 32 bit binaries that could handle long filenames the original 16
bit DOS executable could not deal with.

-- 
ir. J.C.A. Wevers
PGP/GPG public keys at http://www.xs4all.nl/~johanw/pgpkeys.html


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-06 Thread Peter Lebbing 
On 06/09/15 10:11, Dongsheng Song wrote:
> On 2015-09-05 17:40, Werner Koch wrote:
>>  - The random number generator may not produce random output.
> 
> Why not trust Windows CryptoAPI (CryptGenRandom) like libressl ?

May I suggest that you take down your compiled 64-bits versions and
issue a warning on the page, alterting people to the fact that Werner
Koch warned you that the random number generator might not work? It's
rather a huge issue, especially when people use your package to generate
their keys.

BTW, AFAIK, GnuPG builds its own random number generator upon the
services provided by the OS. It doesn't make sense (to me at least) to
make an exception for 64-bit Windows and swap it out for the OS provided
service there.

Is there any reason to provide 64-bits binaries, BTW? It's an unbiased
question, I simply don't know. Does it provide any benefits?

Peter.

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-06 Thread Dongsheng Song 
On 2015-09-05 17:40, Werner Koch wrote:
> On Sat,  5 Sep 2015 04:23, dongsheng.s...@gmail.com said:
>
>> It's really works, you can check my building results:
> No, it can't work:
>
>  - The random number generator may not produce random output.

Why not trust Windows CryptoAPI (CryptGenRandom) like libressl ?

https://github.com/libressl-portable/openbsd/blob/master/src/lib/libcrypto/crypto/getentropy_win.c

If you do not trust CryptoAPI (CryptGenRandom), you can use CNG
(BCryptGenRandom) instead.

CryptGenRandom  [Windows XP/2003 or later]
BCryptGenRandom [Windows Vista/2008 or later] [Cryptography API: Next
Generation
]


https://msdn.microsoft.com/en-us/library/windows/desktop/aa379942(v=vs.85).aspx
https://msdn.microsoft.com/en-us/library/windows/desktop/aa375458(v=vs.85).aspx

>  - GnuPG casts pointers to integers which does not work on 64 bit
>Windows where a pointer (and thus a HANDLE) is 64 bit but int and
>long are 32 bit.
>
>  - There are related problems related to different kind of file
>decriptors.

In theory, you are right. But ALL Windows kernel object include HANDLE
lower than 2^24.
Then if these cast is safe for 64 bit Linux, then safe for Windows too.

https://msdn.microsoft.com/en-us/library/windows/desktop/ms724485(v=vs.85).aspx

>
>> http://sourceforge.net/projects/osb/files/package/portable/gnupg/
>  1. Please add the full source code to the download section or
> otherwise fulfill the requirements of the GPL.
>
>  2. In the summary page you state that the license is CC BY-SA.
> However, both GCC and GnuPG are under the GPL.  You need to fix
> that!
>

Thanks, fixed.




signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-05 Thread Werner Koch 
On Sat,  5 Sep 2015 04:23, dongsheng.s...@gmail.com said:

> It's really works, you can check my building results:

No, it can't work:

 - The random number generator may not produce random output.

 - GnuPG casts pointers to integers which does not work on 64 bit
   Windows where a pointer (and thus a HANDLE) is 64 bit but int and
   long are 32 bit.

 - There are related problems related to different kind of file
   decriptors.

> http://sourceforge.net/projects/osb/files/package/portable/gnupg/

 1. Please add the full source code to the download section or
otherwise fulfill the requirements of the GPL.

 2. In the summary page you state that the license is CC BY-SA.
However, both GCC and GnuPG are under the GPL.  You need to fix
that!


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-04 Thread Dongsheng Song 
On Wed, Sep 2, 2015 at 11:53 PM, Werner Koch  wrote:
> On Wed,  2 Sep 2015 11:17, dongsheng.s...@gmail.com said:
>
>> Yes, I build gnupg 2.1.7 for 32 bit and 64 bit Windows with the latest
>> libgcrypt and pinentry.
>
> Funny, 64 bit Windows is not supported by GnuPG.
>

It's really works, you can check my building results:

http://sourceforge.net/projects/osb/files/package/portable/gnupg/

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-02 Thread Werner Koch 
On Wed,  2 Sep 2015 18:30, t...@riseup.net said:

> Sounds almost reasonable. But why then GnuPG shows Ed25519 keys as eg.
> 'ed25519/52275F7A'? When someone trying to generate 'Curve25519-signing
> key' they'll get ed25519 key. "Maybe I've done something wrong? I should

Well, given that you used --expert we can assume that you know what you
are doing ;-)

> regenerate my signature key...". In my opinion it's a little bit confusing.
> The fact that both Ed25519 and Curve25519 are based on the same curve

The real difference is that Ed25519 uses EdDSA and not ECDH or ECDSA.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-02 Thread Werner Koch 
On Wed,  2 Sep 2015 11:17, dongsheng.s...@gmail.com said:

> Yes, I build gnupg 2.1.7 for 32 bit and 64 bit Windows with the latest
> libgcrypt and pinentry.

Funny, 64 bit Windows is not supported by GnuPG.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-02 Thread Ivan Markin 
Werner Koch:
> That is actually on purpose.  Both are based on the same curve and it
> seems easier to just call it Curve25519 than to explain why we use a
> different variant for signing.  After all Curve25519 is a well known
> term.
Sounds almost reasonable. But why then GnuPG shows Ed25519 keys as eg.
'ed25519/52275F7A'? When someone trying to generate 'Curve25519-signing
key' they'll get ed25519 key. "Maybe I've done something wrong? I should
regenerate my signature key...". In my opinion it's a little bit confusing.
The fact that both Ed25519 and Curve25519 are based on the same curve
one can easily note from '25519' in their names.
Actually Ed25519 is a birational equivalent to Curve25519; it's not a
Curve25519. So I think that GnuPG should use exact naming for what it uses.

-- 
Ivan Markin



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-02 Thread Werner Koch 
On Wed,  2 Sep 2015 03:37, t...@riseup.net said:
> I'm also not able to generate keys in 2.1.7 on my Gentoo machine. It
> generates Ed25519 without errors (a typo: GnuPG says that it would use
> Curve25519 for signature not Ed25519). Because there is no option to

That is actually on purpose.  Both are based on the same curve and it
seems easier to just call it Curve25519 than to explain why we use a
different variant for signing.  After all Curve25519 is a well known
term.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-02 Thread Andre Heinecke 
Hi,

On Monday, August 31, 2015 07:07:03 PM Andre Heinecke wrote:
> If I use the pinentry-basic included in the gnupg-w32 installer I get the
> "No pinentry" error.
> So it looks like pinentry-basic also has a Problem on Windows > 8.1

This was a problem in my test setup. I probably had gpg4win installed when the 
agent was started and so it tried to use the pinentry from gpg4win even after 
I uninstalled gpg4win.

Such things will be solved when gpg4win gets proper 2.1 support. After 
restarting the gpg-agent it picked up pinentry-basic and it worked fine.

If you look at gpg-agent's debug output it will show you which pinentry it 
tries to start.

Regards,
Andre

-- 
Andre Heinecke |  ++49-541-335083-262  | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

signature.asc
Description: This is a digitally signed message part.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-02 Thread Dongsheng Song 
On 2015-09-02 14:33, NIIBE Yutaka wrote:
> On 09/02/2015 10:37 AM, Ivan Markin wrote:
>> I'm also not able to generate keys in 2.1.7 on my Gentoo machine. It
>> generates Ed25519 without errors (a typo: GnuPG says that it would use
>> Curve25519 for signature not Ed25519). Because there is no option to
>> create Curve25519 at the beginning with Ed25519 one I'm trying to
>> `addkey` later. Error seems to have same origins as Windows one:
> This is different issue, I believe.
>
> To create key for Curve25519 encryption, you need development version
> of libgcrypt (from git.gnupg.org).

Yes, I build gnupg 2.1.7 for 32 bit and 64 bit Windows with the latest
libgcrypt and pinentry.
Both them can create key for Curve25519 encryption on my Windows 10 2015
LTSB.




signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-01 Thread NIIBE Yutaka 
On 09/02/2015 10:37 AM, Ivan Markin wrote:
> I'm also not able to generate keys in 2.1.7 on my Gentoo machine. It
> generates Ed25519 without errors (a typo: GnuPG says that it would use
> Curve25519 for signature not Ed25519). Because there is no option to
> create Curve25519 at the beginning with Ed25519 one I'm trying to
> `addkey` later. Error seems to have same origins as Windows one:

This is different issue, I believe.

To create key for Curve25519 encryption, you need development version
of libgcrypt (from git.gnupg.org).
-- 

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-01 Thread Ivan Markin 
I'm also not able to generate keys in 2.1.7 on my Gentoo machine. It
generates Ed25519 without errors (a typo: GnuPG says that it would use
Curve25519 for signature not Ed25519). Because there is no option to
create Curve25519 at the beginning with Ed25519 one I'm trying to
`addkey` later. Error seems to have same origins as Windows one:



gpg (GnuPG) 2.1.7; Copyright (C) 2015 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Secret key is available.

sec  ed25519/125F3B9D
 created: 2015-09-02  expires: 2016-09-01  usage: C
 trust: ultimate  validity: ultimate
[ultimate] (1). Ivan Markin 

gpg> addkey
Please select what kind of key you want:
   (3) DSA (sign only)
   (4) RSA (sign only)
   (5) Elgamal (encrypt only)
   (6) RSA (encrypt only)
   (7) DSA (set your own capabilities)
   (8) RSA (set your own capabilities)
  (10) ECC (sign only)
  (11) ECC (set your own capabilities)
  (12) ECC (encrypt only)
  (13) Existing key
Your selection? 12
Please select which elliptic curve you want:
   (1) Curve 25519
   (2) NIST P-256
   (3) NIST P-384
   (4) NIST P-521
   (5) Brainpool P-256
   (6) Brainpool P-384
   (7) Brainpool P-512
Your selection? 1
gpg: WARNING: Curve25519 is not yet part of the OpenPGP standard.
Use this curve anyway? (y/N) yes
Please specify how long the key should be valid.
 0 = key does not expire
= key expires in n days
  w = key expires in n weeks
  m = key expires in n months
  y = key expires in n years
Key is valid for? (0) 1y
Key expires at Thu 01 Sep 2016 01:22:10 AM
Is this correct? (y/N) y
Really create? (y/N) y
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: agent_genkey failed: Invalid flag
gpg: Key generation failed: Invalid flag


-- 
Ivan Markin



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-01 Thread Ivan Markin 
I'm also not able to generate keys in 2.1.7 on my Gentoo machine. It
generates Ed25519 without errors (a typo: GnuPG says that it would use
Curve25519 for signature not Ed25519). Because there is no option to
create Curve25519 at the beginning with Ed25519 one I'm trying to
`addkey` later. Error seems to have same origins as Windows one:



gpg (GnuPG) 2.1.7; Copyright (C) 2015 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Secret key is available.

sec  ed25519/125F3B9D
 created: 2015-09-02  expires: 2016-09-01  usage: C
 trust: ultimate  validity: ultimate
[ultimate] (1). Ivan Markin 

gpg> addkey
Please select what kind of key you want:
   (3) DSA (sign only)
   (4) RSA (sign only)
   (5) Elgamal (encrypt only)
   (6) RSA (encrypt only)
   (7) DSA (set your own capabilities)
   (8) RSA (set your own capabilities)
  (10) ECC (sign only)
  (11) ECC (set your own capabilities)
  (12) ECC (encrypt only)
  (13) Existing key
Your selection? 12
Please select which elliptic curve you want:
   (1) Curve 25519
   (2) NIST P-256
   (3) NIST P-384
   (4) NIST P-521
   (5) Brainpool P-256
   (6) Brainpool P-384
   (7) Brainpool P-512
Your selection? 1
gpg: WARNING: Curve25519 is not yet part of the OpenPGP standard.
Use this curve anyway? (y/N) yes
Please specify how long the key should be valid.
 0 = key does not expire
= key expires in n days
  w = key expires in n weeks
  m = key expires in n months
  y = key expires in n years
Key is valid for? (0) 1y
Key expires at Thu 01 Sep 2016 01:22:10 AM
Is this correct? (y/N) y
Really create? (y/N) y
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: agent_genkey failed: Invalid flag
gpg: Key generation failed: Invalid flag


-- 
Ivan Markin



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-09-01 Thread Werner Koch 
On Mon, 31 Aug 2015 21:01, aheine...@intevation.de said:

> I think you can't. I've already complained to Werner several times
> that I find the aspect that only "Developers" or the original reporter
> can add information to a bug report hurts bugs.g10code.com

This is done for a reason: In the past we have seen automatically
created spam accounts spamming existing bug reports.  That is very
annoying and thus we have the "Provisional User" role.  I usually grant
full user access as soon as I see a new bug report (for an admin
account a "[P]" and a link to the user is shown in this case).  I have
been traveling the last days, thus the delays.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-08-31 Thread Juan Miguel Navarro Martínez 
On 2015-08-31 at 21:01, Andre Heinecke wrote:
> 2010 I guess is slightly different as it has the "No Pinentry" Problem so 
> I've 
> left that out.
> 
> Regards,
> Andre
> 

It could be or at least part of it may be different.

I know that I also get the "gpg: error getting the KEK: Input/output
error" when trying to import a file with multiple secret files on it
(like when you do `gpg --export-secret-keys`).

Just try it, create multiple secret keys with passphrase on GnuPG 1.4
(or GnuPG 2.0 with GPG4Win if you are fine with the rebooting after
uninstall) then install GnuPG 2.1 and try any command that may cause the
secring.gpg migration. I don't remember if I got or not any pinentry
window during migration.

-- 
Juan Miguel Navarro Martínez

GPG Keyfingerprint:
5A91 90D4 CF27 9D52 D62A
BC58 88E2 947F 9BC6 B3CF



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-08-31 Thread Andre Heinecke 
Hi,

On Monday, August 31, 2015 08:26:31 PM Juan Miguel Navarro Martínez wrote:
> I don't know how to reply to the issue (or maybe I just can't),

I think you can't. I've already complained to Werner several times that I find 
the aspect that only "Developers" or the original reporter can add information 
to a bug report hurts bugs.g10code.com

> I wanted
> to say that issues 2083[1], 2010[2] and 1819[3] may be related or just
> the same. They all have the "End of file" error.
> 
> [1]: https://bugs.gnupg.org/gnupg/issue2083
> [2]: https://bugs.gnupg.org/gnupg/issue2010
> [3]: https://bugs.gnupg.org/gnupg/issue1819

Thanks for that list! I guess I just opened another duplicate for this
with issue 2085 :-o (Damn I thought I knew how roundup search worked but i did 
not find these.)
I've consolidated them in 2085 (because that was my bug ;-) )

2010 I guess is slightly different as it has the "No Pinentry" Problem so I've 
left that out.

Regards,
Andre

-- 
Andre Heinecke |  ++49-541-335083-262  | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-08-31 Thread Juan Miguel Navarro Martínez 
I don't know how to reply to the issue (or maybe I just can't), I wanted
to say that issues 2083[1], 2010[2] and 1819[3] may be related or just
the same. They all have the "End of file" error.

[1]: https://bugs.gnupg.org/gnupg/issue2083
[2]: https://bugs.gnupg.org/gnupg/issue2010
[3]: https://bugs.gnupg.org/gnupg/issue1819

On 2015-08-31 at 18:44, Andre Heinecke wrote:
> Hi,
> 
> On Monday, August 31, 2015 01:49:06 PM Zero0 wrote:
>> I cleared the AppData and registry, installed
>> https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.1.7_20150811.exe to
>> D:\Program Files (x86)\GnuPG, started the command prompt, typed "gpg
>> --full-gen-key --expert" and get an EOF error after I entered the
>> password.
> 
> I can confirm your Problem. Even without full-gen-key or any special options.
> 
> I've opened an issue for this:
> https://bugs.gnupg.org/gnupg/issue2085
> 
> Regards,
> Andre
> 

-- 
Juan Miguel Navarro Martínez

GPG Keyfingerprint:
5A91 90D4 CF27 9D52 D62A
BC58 88E2 947F 9BC6 B3CF



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-08-31 Thread Juan Miguel Navarro Martínez 
On 2015-08-31 at 19:07, Andre Heinecke wrote:
> Hi,
> 
> On Monday, August 31, 2015 01:53:48 PM Juan Miguel Navarro Martínez wrote:
>> I assume you are using a Windows 8 or higher. I already reported that on
>> another message in this same list. For some reason, making a passphrase
>> protected key makes GPG Agent crash.
> 
> I think this is a different bug. When I use a pinentry from gpg4win I run 
> into 
> the gpg-agent crash described in this thread but still can do things that 
> involve pinentry like signing.
> 

I've got no issues either using GPG4Win (Full) nor GPG4Win (Vanilla) on
Windows 10 x64 and the pinentry windows looks different, first uses a
Kleopatra-looking pinentry window, the other a GnuPG-2.1-like with the
GnuPG blue symbol.

-- 
Juan Miguel Navarro Martínez

GPG Keyfingerprint:
5A91 90D4 CF27 9D52 D62A
BC58 88E2 947F 9BC6 B3CF



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-08-31 Thread Andre Heinecke 
Hi,

On Monday, August 31, 2015 01:53:48 PM Juan Miguel Navarro Martínez wrote:
> I assume you are using a Windows 8 or higher. I already reported that on
> another message in this same list. For some reason, making a passphrase
> protected key makes GPG Agent crash.

I think this is a different bug. When I use a pinentry from gpg4win I run into 
the gpg-agent crash described in this thread but still can do things that 
involve pinentry like signing.

If I use the pinentry-basic included in the gnupg-w32 installer I get the "No 
pinentry" error.
So it looks like pinentry-basic also has a Problem on Windows > 8.1

I've not reported a bug for this but I keep it in mind. (The issues are likely 
related)

Works fine on Windows 7 though, curious.

Regards,
Andre

-- 
Andre Heinecke |  ++49-541-335083-262  | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-08-31 Thread Andre Heinecke 
Hi,

On Monday, August 31, 2015 01:49:06 PM Zero0 wrote:
> I cleared the AppData and registry, installed
> https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.1.7_20150811.exe to
> D:\Program Files (x86)\GnuPG, started the command prompt, typed "gpg
> --full-gen-key --expert" and get an EOF error after I entered the
> password.

I can confirm your Problem. Even without full-gen-key or any special options.

I've opened an issue for this:
https://bugs.gnupg.org/gnupg/issue2085

Regards,
Andre

-- 
Andre Heinecke |  ++49-541-335083-262  | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: GnuPG modern can't genereate keys on my Windows

2015-08-31 Thread Juan Miguel Navarro Martínez 
I assume you are using a Windows 8 or higher. I already reported that on
another message in this same list. For some reason, making a passphrase
protected key makes GPG Agent crash.

On 2015-08-31 at 07:49, Zero0 wrote:
> I cleared the AppData and registry, installed 
> https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.1.7_20150811.exe to 
> D:\Program Files (x86)\GnuPG, started the command prompt, typed "gpg 
> --full-gen-key --expert" and get an EOF error after I entered the password.
> gpg (GnuPG) 2.1.7; Copyright (C) 2015 Free Software Foundation, Inc.
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Please select what kind of key you want:
>(1) RSA and RSA (default)
>(2) DSA and Elgamal
>(3) DSA (sign only)
>(4) RSA (sign only)
>(7) DSA (set your own capabilities)
>(8) RSA (set your own capabilities)
>(9) ECC and ECC
>   (10) ECC (sign only)
>   (11) ECC (set your own capabilities)
> Your selection? 9
> Please select which elliptic curve you want:
>(2) NIST P-256
>(3) NIST P-384
>(4) NIST P-521
>(5) Brainpool P-256
>(6) Brainpool P-384
>(7) Brainpool P-512
> Your selection? 2
> Please specify how long the key should be valid.
>  0 = key does not expire
> = key expires in n days
>   w = key expires in n weeks
>   m = key expires in n months
>   y = key expires in n years
> Key is valid for? (0) 4y
> Key expires at 08/30/19 12:23:32 China Standard Time
> Is this correct? (y/N) y
> GnuPG needs to construct a user ID to identify your key.
> Real name: Anonymous
> Email address: a...@example.com
> Comment:
> You selected this USER-ID:
> "Anonymous "
> Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
> We need to generate a lot of random bytes. It is a good idea to perform
> some other action (type on the keyboard, move the mouse, utilize the
> disks) during the prime generation; this gives the random number
> generator a better chance to gain enough entropy.
> gpg: agent_genkey failed: End of file
> Key generation failed: End of file
> 
> 
> 
> ___
> Gnupg-users mailing list
> Gnupg-users@gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
> 

-- 
Juan Miguel Navarro Martínez

GPG Keyfingerprint:
5A91 90D4 CF27 9D52 D62A
BC58 88E2 947F 9BC6 B3CF



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

GnuPG modern can't genereate keys on my Windows

2015-08-31 Thread Zero0 
I cleared the AppData and registry, installed 
https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.1.7_20150811.exe to D:\Program 
Files (x86)\GnuPG, started the command prompt, typed "gpg --full-gen-key 
--expert" and get an EOF error after I entered the password.
gpg (GnuPG) 2.1.7; Copyright (C) 2015 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Please select what kind of key you want:
   (1) RSA and RSA (default)
   (2) DSA and Elgamal
   (3) DSA (sign only)
   (4) RSA (sign only)
   (7) DSA (set your own capabilities)
   (8) RSA (set your own capabilities)
   (9) ECC and ECC
  (10) ECC (sign only)
  (11) ECC (set your own capabilities)
Your selection? 9
Please select which elliptic curve you want:
   (2) NIST P-256
   (3) NIST P-384
   (4) NIST P-521
   (5) Brainpool P-256
   (6) Brainpool P-384
   (7) Brainpool P-512
Your selection? 2
Please specify how long the key should be valid.
 0 = key does not expire
= key expires in n days
  w = key expires in n weeks
  m = key expires in n months
  y = key expires in n years
Key is valid for? (0) 4y
Key expires at 08/30/19 12:23:32 China Standard Time
Is this correct? (y/N) y
GnuPG needs to construct a user ID to identify your key.
Real name: Anonymous
Email address: a...@example.com
Comment:
You selected this USER-ID:
"Anonymous "
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: agent_genkey failed: End of file
Key generation failed: End of file___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users