ASN.1 isn’t a schema language. ASN.1 retroactively bolted on a schema language I can’t use to generate code in all popular languages.
-
-
Why do you say that? It's just a simple matter of coding to implement
1 reply 0 retweets 0 likes -
2 replies 0 retweets 0 likes
-
The point being?
1 reply 0 retweets 0 likes -
RCERCERCERCERCE RCERCERCERCERCE RCERCERCERCERCE RCERCERCERCERCE RCERCERCERCERCE RCERCERCERCERCE RCERCERCERCERCE RCERCERCERCERCE
1 reply 0 retweets 1 like -
All of the critical infrastructure computing is insecure because people keep fucking up X.509 parsers. That is the problem. But the real problem is X.509 (and vicariously ASN.1) advocates can’t even admit there is a problem.pic.twitter.com/tWytIL1gz5
2 replies 4 retweets 9 likes -
I don't disagree
1 reply 0 retweets 2 likes -
Seems like you can’t admit there’s a problem. And really, that’s the core problem. Nobody wants to talk about it, and meanwhile the world burns with unpatchable bootloader, firmware, and baseband vulnerabilities.
2 replies 0 retweets 0 likes -
I'm more worried about the world not admitting that there's a solution! Would CA/B forum be the place to propose replacing ASN.1 in certs? has It ever come up? has it basically no chance due to inertia?
3 replies 0 retweets 1 like
Personally I’d love protobufs for this!
-
-
Last I checked protobufs are non-canonical and can't be parsed without a schema (as inner objects are just byte arrays). Both of those things are major issues IMHO.
0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.