3 ms·
Yes, assuming someone captured the malicious certificate and checked. Which would have happened in this case now (after someone forgot to renew), but likely not
by tgsovlerkhgsel 3y ago
Yes, assuming someone captured the malicious certificate and checked. Which would have happened in this case now (after someone forgot to renew), but likely not before.
Browsers would happily accept it and IIRC they don't check against the logs.
- aaomidi 3y agoYep - this is all because of the delayed insertion into the CT tree :(