It’s a critical failure being returned as a mostly untyped non-blocking comment.
-
-
Replying to @dakami
Lies. Both an incorrect MDC and the lack of an MDC return DECRYPTION_FAILED, FAILURE, and a nonzero exit status. That's three different ways you know stuff went wrong, including the standard for shell commands. Ignoring exit status is terrible practice.pic.twitter.com/PlOnadkznV
3 replies 1 retweet 10 likes -
Replying to @marcan42
Ok well, what was the success rate of your claimed API defense?
1 reply 0 retweets 0 likes -
Replying to @dakami
This would've literally happened to *any* API with a streaming design. All the available error signaling mechanisms were used. It doesn't matter if it's text or C functions. If the caller chooses to ignore error codes, that's the caller's fault.
1 reply 0 retweets 1 like -
Replying to @marcan42
No, it wouldn’t have happened in any API that blocked plaintext retrieval by default, like modern anything does.
1 reply 0 retweets 0 likes -
Replying to @dakami
We've already gone over how gpg supports streaming for huge files (and yes, people *do* use this feature. All the time. Dumping huge backup tarballs through gpg is quite standard practice.)
1 reply 0 retweets 1 like -
Replying to @marcan42
Shit didn’t work. Don’t care why not. Shit didn’t work for anyone downstream of gpg. Do care where not.
1 reply 0 retweets 1 like -
Replying to @dakami
I just don't think piling on gnupg when they did everything reasonably within their design is useful. Sometimes all the downstream users just fuck things up ¯\_(ツ)_/¯
1 reply 0 retweets 4 likes -
Replying to @marcan42
It’s not about piling on. There’s an old textpipe interface mode that doesn’t work very well, and there aren’t exactly resources to replace. The game is dispassionately understanding the engineering problems and not just blamestorming.
1 reply 0 retweets 4 likes -
Replying to @dakami
Okay, so what's the plan here? Convert it to a shared library, hope people pay attention to *those* return codes? Add a non-streaming command line option (and plead everyone uses it)? How is this better than just checking the damn exit code?
2 replies 0 retweets 3 likes
I'd understand if this were some subtle implication of the pipe interface, but we're literally talking about ignoring exit status here. This is security tool 101. Heck it's programming 101. Check your error codes.
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.