I can replicate the error by 2.2.35, but I cannot replicate it with rG7b1db7192.
I tested:
- GNU/Linux
- i686
- x86_64
- Windows
- i686
I can replicate the error by 2.2.35, but I cannot replicate it with rG7b1db7192.
I tested:
I pushed the change needed for GnuPG to t5964 branch.
See: https://dev.gnupg.org/rGc281bd94349e4f7997a89927aaa2c2f45004b902
Added HKDF implementation to master.
Applied to 1.10 branch.
didn't seem to work with 1.9.x
In the branch https://dev.gnupg.org/source/Scute/history/t6002/ , by the commit rS123d617ebefe: Less administration of devices by scute., things has been changed.
Thank you. Applied.
I realized that we need to invent a way to represent KEYGRIP (40-byte string) in the scheme of PKCS#11; PKCS#11 uses fixed-size string (space padded) for it's label (32) and serialno (16). Basically, it identifies the device by slot number.
Because it's the library which refuses null passphrase as input, only possible options are either:
Backported to GnuPG 2.2.
Applied the changes.
Now, it also supports a reader with pinpad.
Created gniibe/t5912 branch.
It works for me.
I can only find this one: https://github.com/patrickfav/singlestep-kdf/wiki/NIST-SP-800-56C-Rev1:-Non-Official-Test-Vectors
See https://github.com/google/xsecurelock/blob/master/helpers/authproto.h
for the interaction between xsecurelock and the helper.
I changed gpg-connect-agent (added --unbuffered option) so that we can write shell script interacting gpg-agent.
Wrote a shell script for xsecurelock's authproto (helper executable):
I take this ticket. The way to go is removing all such cases.
Reference to a CVE for old MinGW-W64: https://nvd.nist.gov/vuln/detail/CVE-2018-1000101
https://sourceforge.net/p/mingw-w64/bugs/709/
Also applied to 1.10.
Applied and pushed.
I learned that it's now called "OneStep KDF" in SP 800-56Cr2.
It's "SSKDF" in OpenSSL (Single Step KDF, perhaps).