4 ms·
If you like this, you will probably be interested in this: Everything you Never Wanted to Know about PKI but were Forced to Find Out, by Peter Gutmann: https:/
by teddyh 5y ago
If you like this, you will probably be interested in this:
Everything you Never Wanted to Know about PKI but were Forced to Find Out, by Peter Gutmann: https://www.cs.auckland.ac.nz/~pgut001/pubs/pkitutorial.pdf https://www.cs.auckland.ac.nz/~pgut001/pubs/pkitutorial.pdf
Also, this, by the same person: X.509 Style Guide (which talks about the two date formats):
“In coming up with the worlds least efficient machine-readable time encoding format, the ISO nevertheless decided to forgo the encoding of centuries, a problem which has been kludged around by redefining the time as UTCTime if the date is 2049 or ealier, and GeneralizedTime if the date is 2050 or later (the original plan was to cut over in 2015, but it was felt that moving it back to 2050 would ensure that the designers were either retired or dead by the time the issue became a serious problem, leaving someone else to take the blame).
To decode a date, if it's UTCTime and the year is less than or equal to 49 it's 20xx, if it's UTCTime and the year is equal to or greater than 50 it's 19xx, and if it's GeneralizedTime it's encoded properly (but shouldn't really be used for dates before 2050 because you could run into interoperability problems with existing software). Yuck.
To make this even more fun, another spec at one time gave the cutover date as 2050/2051 rather than 2049/2050, and allowed GeneralizedTime to be used before 2050 if you felt you could get away with it. It's likely that a lot of
conforming systems will briefly become nonconforming systems in about half a centuries time, […]”
— https://www.cs.auckland.ac.nz/~pgut001/pubs/x509guide.txt https://www.cs.auckland.ac.nz/~pgut001/pubs/x509guide.txt
- Joker_vD 5y agoPretty much everything about X.500 is breathtakingly terrifying. How did people even manage to come up with it?
- teddyh 5y agoIIUC, all the old ISO/ITU telecommunication standards were like that. This is why people fled in droves to instead use and implement TCP/IP from the RFCs.
- Joker_vD 5y agoOh yeah, Gutmann actually explains this history in one of his writings, and then the certificates kinda start making sense. Also, remember the OSI model? It was not supposed to be just a model — and it's a failure of the model anyway, real network protocols just keep piling up application layers on top of each other, the upper ones using the lower ones as their transport layers, — no, there were supposed to be actual separate protocols for each level, and actually there are! Of course, nobody sane ever uses them.
- commandlinefan 5y ago> How did people even manage to come up with it? Reminds me of the old saying: a zebra is a horse designed by committee.
- deleted 5y ago[deleted]