> I was wondering if anyone could tell me if it is in fact possible to
> verify a signature created using WTLS-8?
> A reference to the specification of this curve can be found here:
> http://technical.openmobilealliance.org/tech/affiliates/wap/wap-261-wtls-20010406-a.pdf
>
> (page 90)
>
>From page 64 of the document you cited:
enum { anonymous(0), ecdsa_sha(1), rsa_sha(2), (255)}
SignatureAlgorithm;
You should be OK with rsa_sha, but its not clear to me if all the ecdsa_sha
are supported. To understand why, you need to look at Table 8 on page 86
and the curves WTLS calls out. I *think* Crypto++ will support about 8 of
the 12 they specify.
> We are currently looking at alternatives to OpenSSL and Crypto++ seems
> like a good way to go.
> I have spent a little time trying to do this in Crypto++ but I have not
> had any success as yet. Before I go any further I thought I'd ask the
> knowledgable folk here.
>
I think it depends on what you want to accomplish.
Are you interested *only* in verifying a signature that's already been
parsed? Or are you interested in the bigger package? Here, the bigger
package includes things like implementing the protocol (sub tasks will
include asynchronous socket I/O, record layer implementation, X.509
parsing, key exchange, bulk transfer, etc).
If its the former, then Crypto++ should do fine. If the latter, then you
are going to have a lot of work because it looks like a re-implementation
of TLS. In the case of the latter, you should evaluate another library.
>From your other message:
> At the moment, all I have is the public key. I can use OpenSSL to dump
> the output of the public key and can convert it to DER format in Crypto++
> and what I pass it through dumpasn1 it matches...
This should help if its in PEM format:
http://www.cryptopp.com/wiki/PEM_Pack. You won't need to use OpenSSL to
convert it to ASN.1/DER.
> eg (I'm not entirely comfortable posting the key in a public forum so I
> have obfuscated some of the detail here):
That's fine. Call out the curve you are using from page 88. Or, post the
OID, Curve Name or domain parameters (Curve, Base Point and Modulus); keep
the Public Point (Q) and the Private Exponent (x) to yourself.
Jeff
--
--
You received this message because you are subscribed to the "Crypto++ Users"
Google Group.
To unsubscribe, send an email to [email protected].
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
---
You received this message because you are subscribed to the Google Groups
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
