What do you mean by "openpgp popup"?
Which installation options did you used whethn installing gpg4win? Depending on
the version you get a different pinentry version - we have a qt based one, a GTK
based base, and a very simple native windows pinentry.
Which Libgcrypt version are you using? ("gpg --version" shows it)
That seems to be a OS/X specific bug in its file systems. I have no idea how to
fix that. Maybe this should go into the FAQ. The obvious workaround is to copy
a pubring.gpg with one key to the MSDOS directory.
Fixed in master. Thanks.
Interesting. Thanks for reporting.
Yes, please close it. Don't know how to answer your mail at the web interface. Sorry for these mistaken reports – I didn't know and I wrote them too fast. I'll try not to
do this in the future.
So what is your problem now? Mistaken report - shall I close it?
You need to perform the bigmath modexp routines in constant time, the same as the
smartcard people do to stop key theft via power usage observation.
To also fix Issue1449, enhance my correction this way:
rc = ldap_set_option(ld, LDAP_OPT_PROTOCOL_VERSION, LDAP_VERSION3);
if (rc)
{
log_error (_("setting LDAPv3 for `%s:%d' failed: %s\n"),
host, port, ldap_err2string (rc));
/* FIXME: Need deinit (ld)? */
return -1;
}
rc = ldap_simple_bind_s (ld, opt.user, opt.pass);
if (rc)
{
log_error (_("binding to `%s:%d' failed: %s\n"),
host, port, ldap_err2string (rc));
/* FIXME: Need deinit (ld)? */
return -1;
}And add translations for the new error message.
Thank you
sorry can't delete
Awesome, thank you!
References:
OpenSSL
http://git.openssl.org/gitweb/?
p=openssl.git;a=blob;f=crypto/ecdsa/ecs_ossl.c;h=adab1f74b41daf6e719ca1fdae1ba81
7085c7802;hb=HEAD#l309
Nettle:
http://git.lysator.liu.se/nettle/nettle/blobs/master/ecc-ecdsa-sign.c#line86
http://git.lysator.liu.se/nettle/nettle/blobs/master/ecc-hash.c
NSS:
https://hg.mozilla.org/projects/nss/file/49360b638350/lib/freebl/ec.c#l746
Done something similar for master; needs to be backported to 1.5.
----Messaggio originale----
Da: gnupg@bugs.g10code.com
Data: 13/12/2013 16.19
A: <gfrisani@libero.it>, <wk@gnupg.org>
Ogg: [issue1578] translation in ItalianWerner Koch <wk@gnupg.org> added the comment:
Send it to translations@gnupg.org. However, it is too late for 1.4.16.
status: unread -> chatting
g10 Code's BTS <gnupg@bugs.g10code.com>
<T1578>
Send it to translations@gnupg.org. However, it is too late for 1.4.16.
Also related (includes patch): http://bugs.debian.org/cgi-bin/bugreport.cgi?
bug=725411
I have pushed a similar change to 2.0 and master. Will also be done for 1.4.
That is work in progress - please don't report bug for master to the tracker.
Werner - taht is the problem - I already tried that (and other hints too) - it
is IMO a lack of a good feature in gpg.
Support is already in master and in the soon to be released 1.6.0
Libgcrypt 1.6 will be released this year.
Retire you old key. There is a "disable" command in "gpg --edit-key".
Fixed with commit ab3fe5d.
The grammar is quite old and should anyway adjusted to modern standard. There
is a separately mainatained toke table which does not make much sense, given
that that it is possible to re-use the bison generated token table. I see what
I can do.
Fixed in the git master branch.
yep - rather an enhancement request then a bug.
OTOH even before the Snowden-era it would be always better to implemented a
strategy to choose the "best" key (in my case the older has 1024 bit - the newer
has 4096).
If no key has been specified, gpg uses the first key it finds.
This is not a bug. It might be nicer if gpg would use a heuristic to select a
newer key but that is not the case and quite some work to implement properly.
Thus better specifiy your key in the gpg.conf.