[Botan-devel] Solved! Botan Patch inside Re: potential problem with 'GOST 3410-2001' parameters, or with my code
bert.hubert at netherlabs.nl
Thu Jan 27 11:01:00 EST 2011
On Thu, Jan 27, 2011 at 10:31:33AM -0500, Jack Lloyd wrote:
> Do you know of any existing GOST test cases which consist of:
> A wire-format (ie octet string, or X.509 cert) key
> A wire-format signature
> A wire-format message
The best case I know comes from RFC 5933 itself. Let me know if the below is
crisp & concise enough, I could work on this a bit more to tighten it up if
The PEM format key in all its little-endian horror (you need to linewrap the
GostAsn1 field from paragraph 2.2 a bit to get this file):
-----BEGIN PRIVATE KEY-----
-----END PRIVATE KEY-----
This corresponds to x =
The unhashed original comes from:
"www.example.net. 3600 IN A 192.0.2.1"
The GOST R34.11 hash that is derived from the packed version of this
The 64 byte signature from the RFC:
This is encoded in DNSSEC RRSIG format as:
www.example.net. 3600 IN RRSIG A 12 3 3600 20300101000000 (
20000101000000 59732 example.net.
Here a signature made with a patched Botan:
Openssl also verifies this one as correct.
> anymore so I don't know what happened; it's quite possible I wrote the
> signature serialization portion myself and made the error there, then
> replicated the buggy behavior into botan.
It is easy enough to encode 'r,s' in that order and not as 's,r'.. One can
take little-endian too far it appears ;-)
More information about the botan-devel