3 ms·
My understanding is yes - if the https page was in CF memory (for decrypting from server and encrypting for user) its contents could have been dumped to a cache
by AlexandrB 10y ago
My understanding is yes - if the https page was in CF memory (for decrypting from server and encrypting for user) its contents could have been dumped to a cache of one of the affected sites.
- omegaworks 10y agoTo be even more clear: if the CF servers had any plaintext in memory, that plaintext might have been compromised. Plaintext could be anything from HTML pages to GET and POST request data (containing auth keys, passwords, JSON blobs, etc.) If CF decrypts information you send to it before encrypting it to your users, that's a step where plaintext might have been present in their servers' memory. (Please correct me if I'm wrong.)
- fiedzia 10y agoAccording to CF, they store certificates and cached content separately, so they were not exposed.
- oldsj 10y agoRight. Clear text data was exposed, not the certificate itself. But who needs a certificate when you have the cleartext?