Thanks for your transparency about being a potentially affected site with this Cloudbleed thing. I hadn't heard about it. It's good to know that you consider the risk to your users is very low. I've changed the passwords on my accounts just in case. Re expiring session cookies - is that something we can do ourselves via the manage login sessions part of our account settings?
Also, the article you've linked to said most of the cloudbleed activity happened between 13th -18th Feb. Within that period I bought a paid account and a large number of icon slots (on another DW account) - would my credit card details, address or anything like that potentially have been exposed IF by some small chance this issue affected my Dreamwidth session? Or journal entries? Or would it just be passwords and or/login cookies. I do realise you think it very unlikely Dreamwidth was affected - I'm just curious about what might have been exposed if you were.
And excelllent news that LJ has whitelisted DW again. :) DW is my journalling home now, but I do still x-post to LJ.
no subject
Also, the article you've linked to said most of the cloudbleed activity happened between 13th -18th Feb. Within that period I bought a paid account and a large number of icon slots (on another DW account) - would my credit card details, address or anything like that potentially have been exposed IF by some small chance this issue affected my Dreamwidth session? Or journal entries? Or would it just be passwords and or/login cookies. I do realise you think it very unlikely Dreamwidth was affected - I'm just curious about what might have been exposed if you were.
And excelllent news that LJ has whitelisted DW again. :) DW is my journalling home now, but I do still x-post to LJ.