You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since SafeEvpPKeyHandle exists to allow interop with OpenSSL, it would be good for callers to be able to determine if they are using the same library/version of OpenSSL that we are.
publicsealedpartialclassSafeEvpPKeyHandle{// The result of SSLeay() (OpenSSL 1.0.2) or OpenSSL_version() (OpenSSL 1.1.x)publicstaticintOpenSslVersion{get;}}
Discussion points:
The native API is Unix C-long, so 32-bit on 32-bit, 64-bit on 64-bit.
So, int, uint, long, or ulong?
The version number contains detail we can't expose via System.Version
Callers are only expected to do ==
The text was updated successfully, but these errors were encountered:
Seems like a strange place to put it. Could we put it on another type with OpenSSL in the name, that's not a SafeHandle, etc.? Even if it meant introducing a new type?
The version number contains detail we can't expose via System.Version
Since SafeEvpPKeyHandle exists to allow interop with OpenSSL, it would be good for callers to be able to determine if they are using the same library/version of OpenSSL that we are.
Discussion points:
int
,uint
,long
, orulong
?==
The text was updated successfully, but these errors were encountered: