idk it seems bad to me that openssl implements both fundamental cryptographic algorithms, *and* a bunch of protocol/policy stuff. seems like they should be separate things. idk
-
Show this thread
-
today I learned it delegates part of the verification process to the caller, after doing its own built-in checks, but this interface is done in a way that means the caller can simply override and ignore the built-in checks
1 reply 0 retweets 4 likesShow this thread -
like I was being flippant when I said I'd simply make it easy to implement correctly but this is the sort of interface that something like this should not have
2 replies 0 retweets 4 likesShow this thread -
as in, you pass a function pointer to openssl, and it calls it with an int saying if its own checks passed or not. your function can simply, ignore this int, if it wants to
1 reply 0 retweets 2 likesShow this thread -
-
Replying to @sgrif
I would simply not pass this int to an untrusted function
1 reply 0 retweets 5 likes -
Replying to @mountain_ghosts @sgrif
ah yeah hmm this server's certificates are all busted. what do you reckon, random piece of code I've not reviewed and have just been linked to
1 reply 0 retweets 2 likes -
Replying to @mountain_ghosts
And by "this server's certificates are all busted" I assume you mean "2"
1 reply 0 retweets 1 like -
Replying to @sgrif
you mean SSLv2, or that openssl is literally calling verify_callback with int 2
1 reply 0 retweets 0 likes
The latter (not necessarily 2 specifically, just musing how little context it's actually able to carry)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.