sm: Fix certificate creation with key on card.
card: Print usage info for each key.
scd: Extend KEYPAIRINFO by key usage info.
card: Print the keyref in the listing.
scd: Don't let the "undefined" app cause a conflict error.
sm: Prepare algo mapping to handle values > 255.
Fixed. Needs to go into the next gpg4win release.
Fix gcc warnings when building for Windows.
Update gpg-error.m4 and create ChangeLog.
Remove GNU-isms from the doc Makefiles.
Update libtool and add usual defines for macOS.
Make C_Sign error handling spec compliant.
Minor updates of the README files.
Change license from GPL with Mozilla exception to LGPL.
core,w32: Fix missing sentinel in dir name builder.
Ah okay, that was Windows were we have a couple of warnings anyway. Must have missed that one.
Aiiih, what happend to the sentinel attribute? I need to check.
Clean up use of label and s/n in CK_TOKEN_INFO.
Properly handle card switching.
Let gpgsm do the actual key selection work.
Libdns is not our own code and our intention was to keep it in sync with upstream. However, after some initial success the upstream author lost interest. We now consider to rework the code to remove a bit of the more creative use of C99 and maybe even get rid of some of the used C99 features (gnupg is mainly C90 with some exceptions).
web: Yet another c+p fix.
Which version of gpa is that?
Rework of some parts to support several keys pers slot.
Silence -Wint-in-bool-context warnings.
Bunch of refactoring and minor changes for PIV cards.
Never clean the GNUPGHOME if it is the standard directory.
Improve t-getslotinfo, t-getslotlist and t-opensession
Define all p11 function without using a macro.
Please try "gpg --quick-gen-key" which takes the user-id on the command line - that uses a different code path.
web: Fix link in previous commit
card: New command "yubikey".
swdb: Release GnuPG 2.2.13 and moved some news to the attic
• werner updated the task description for
T4290: Release GnuPG 2.2.13.
• werner renamed
T4290: Release GnuPG 2.2.13 from
Release GnuPG 2.1.13 to
Release GnuPG 2.2.13.
scd: Implement decryption for PIV cards.
swdb: Release libassuan 2.5.3
sm: In --gen-key with "key from card" show also the algorithm.
common: Provide function to get public key algo names in our format.
common: New functions get_option_value and ascii_strupr.
scd: Make app_genkey and supporting ISO function more flexible.
scd: Fix parameter name of app_change_key.
scd: Allow standard keyref scheme for app-openpgp.
gpg: Emit an ERROR status if no key was found with --list-keys.
New error codes NO_AUTH and BAD_AUTH
scd: For PIV cards used NO_AUTH instead of BAD_PIN.
I don't think that we are going to change this. All data is utf-8 including the *conf files.
• werner renamed
T1563: Place content of doc/DETAILS at www.gnupg.org from
"pub", "uid", "sub"... definition missing on GnuPG website documentation to
Place content of doc/DETAILS at www.gnupg.org.
Sure, but lets use that ticket for this. if you have another topic, feel free to open another ticket.
scd: Implement RSA signing for PIV cards.
sm: In --gen-key with "key from card" show also the algorithm.
common: Provide function to get public key algo names in our format.
card: Make "generate" work for PIV cards.
scd: Allow generating ECC curves on PIV cards.
common: New functions get_option_value and ascii_strupr.
card: Print the used algorithm of all keys.
card: Fix a NULL-ptr deref in key listings.
scd: Store a new PIV public key in the certificate DO.
card: Support reading and writing PIV certificates
card: Add readline completion for help arguments
scd: Add genkey command to app-piv (rsa-only)
scd: Make app_genkey and supporting ISO function more flexible.
scd: Fix parameter name of app_change_key.
doc: Add basic man page for the gpg-card-tool.
See also T4013 which is about ed25519 key support
scd: Implement PIN changing and unblocking for PIV cards.
scd: Allow standard keyref scheme for app-openpgp.
It is in the tarball:
and for example Debian installs it as /usr/share/doc/gnupg/DETAILS.gz. Check out the first section "Format of the colon listings". Or use GPGME which provides C, C++, Python and JSON bindings. Sorry, it never made it to the website.
@kristianf we talked about this on Saturday evening. Would you be so kind and have a quick look at the problem with the hu server?
build: Fix for Microsoft MSVC.
Okay, I see the problem. The microsoft toolchain is more picky about de-facto standard use patterns with common blocks and the author of that code was not ware of this. Thanks for reporting, will be fixed in the next release.
Despite that I created this task, I am still not not convinced that removing the term passphrase is a good idea. If we do this in gnupg we would need to change all strings to make it clear that the passphrase is used to protect one's own key and has nothing to do with encryption etc. In fact the term PIN would be better because it is common knowledge that you use a PIN to get access to something you own. There would be less confusion on the purpose of the passphrase. Sure PIN is usually considered to be a number. However my bank allows a string to be used as, what they call, PIN.
This function is not exported on purposes. Even the name of the header file indicates that tis is internal. External, that is public functions of the API, are defined gpgrt.h and only made externally visible by including them in the .def file. This has not been done and so I don't understand your bug report.
web: Fix top menu alignment.
web: Try to fix sub-menus for touch screens
web: Change URL of g10 Code in the service page.
• werner committed
rEd8b64613d992: po: Update Polish translation (authored by Jakub Bogusz <qboosh@pld-linux.org>).
po: Update Polish translation
• werner committed
rG900ae94797ed: po: Update Polish translation (authored by Jakub Bogusz <qboosh@pld-linux.org>).
po: Update Polish translation
card: Implement non-interactive mode.
card: New command 'authenticate'.
scd: Add DES authentication for PIV card.
swdb: Try to detect duplicate entries
card: Cache the results from gpg and gpgsm.
According to sks-keyservers.net both servers you mention run the very same software. Thus I would like to understand why you think they require the use of a legacy option.