From safestack.h, line 113, in 1.0 beta 3:
typedef char *STRING;
typedef const char *CSTRING;
Using such generic names seems like a really bad idea - its asking for
conflicts. And they do happen, at least on windows. The problem is
that one of the windows headers, ntsecapi.h around line
Thor Lancelot Simon wrote:
Can I assume that any data returned when I access the DN of a peer's
certificate using OpenSSL are ASCII or UTF8?
No, see Howards posts.
If not, how do I tell
the difference?
I think I understand that DNs not encoded as UTF8String should not
have high-bit
