juan_lang at yahoo.com
Fri Nov 17 18:12:51 CST 2006
> I'm just looking into implementing Kerberos and Negotiate for SSPI. It
> seems like I'll need an ASN.1 parser for both of those. I know you have
> a partial implementation of an ASN.1 DER parser in crypt32, but I think
> it would be kind of silly to keep two seperate copies. Think it would
> make sense to create our own asn dll? Or is there any method to find out
> what functions msasn1.dll provides?
Well, finding out the functions is easy enough: winedump can do that for
you. The trouble is they're undocumented. Some very sparse information
is available for at least one function  based on describing a
vulnerability someone discovered in msasn1.dll. You could use that as a
starting point for test cases for msasn1, and you could implement one
based on those.
I think you could get Kerberos and Negotiate working quicker just by
copying code as needed. No non-MS application I'm aware of uses msasn1
directly, so Wine wouldn't gain much from a compatible version. Doing the
"right" thing could be sort of a hassle for crypt32 too (not that so many
apps use it right now.)
The only thing is how much duplicated code offends you. I'm trying to
prevent you from diving into a black hole, like I did with crypt32 when
what I was really after was SSL ;)
Online degrees - find the right program to advance your career.
More information about the wine-devel