4 ms·
Sometimes a document is actually no longer confidential, and there’s a newer version without the watermark, but accidentally the older version is the one that g
by derefr 7y ago
Sometimes a document is actually no longer confidential, and there’s a newer version without the watermark, but accidentally the older version is the one that gets shared/linked to. (Usually the only difference is the watermark; we’re not talking about documents that get redacted for public consumption here.)
I encounter this problem pretty frequently with System-on-Chip spec sheets. They’re confidential while under development; and still confidential while being floated for sale by private negotiation to private device makers; but once they’re in a production device, those devices will have their own public PR pages describing exactly the properties of the SoC, so the SoC can’t really hide its specs any more at that point.
So, once the SoC manufacturer makes a high-profile sale, they will usually “declassify” the spec... in the sense of allowing the release of the spec sheet. But they don’t usually bother to ever publish a copy of the de-watermarked spec sheet at any canonical URL; they only begin sending the de-watermarked sheet in place of the watermarked one to new customers.
So, when you find one of these spec sheets online, they’re just as likely to be a copy that a device maker got from the SoC manufacturer from before the specs were declassified, which they released once they were told it was okay to do so. And such documents still have the “confidential” / “not for public release” watermark.
- dreamcompiler 7y agoSo it's analogous to the key revocation problem, but more like a key invocation problem.