summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorWerner Koch <wk@gnupg.org>2011-06-13 12:33:08 +0200
committerWerner Koch <wk@gnupg.org>2011-06-13 12:33:08 +0200
commitc4bce4aa60e62b55e2f7781a2aa55c2e30db2112 (patch)
tree759fe764ec678f2bbb43e58b40a5bc2e9b1b0109 /doc
parentf796e9877e7e065b23dee68184e46a4307d9dfa9 (diff)
downloadlibgcrypt-c4bce4aa60e62b55e2f7781a2aa55c2e30db2112.tar.gz
Fixed a pkcs#1 v1.5 flaw regarding leading zero bytes
With these changes the entire new pkcs#1 test suite passes fine. The leading zero bytes used to appear due to mixed signed/unsigned use of our internal representation of the values as MPIs. The changed code also detected another bug in the DSA selftest which used the pkcs1 flag - this was certainly wrong but didn't throw an error. The code in GnuPG does the right thing thus I believe not too many applications got it as wrong as we in our own selftest.
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions