3 ms·
In an e-mail to eNom's google-clients-specific support address dated 6/18/13, I informed them that I wished to transfer a domain away from them, and I said: "P
by kentonv 12y ago
In an e-mail to eNom's google-clients-specific support address dated 6/18/13, I informed them that I wished to transfer a domain away from them, and I said:
"PS. The reason I am transferring is because I signed up for whois protection yet my whois info has not been protected. From what I can find on the internet, this is a common problem with Google Apps, Google will not respond to support requests for free domains, and the only way I can fix it is by taking control myself. :("
Now two years later this problem is "discovered" by someone else and Google is treating it as a security disclosure? Hey Google, maybe you should have listened to the people all over your own fucking support forums that have been complaining about this for years?
- nikcub 12y agoThis was the same with Superfish. If you look at the Lenovo forums and other websites (Google search Superfish and set the time to before 2015) you'd find tons of complaints from users. In these instances it was only when somebody recognized these issues as being real security issues and repackaged them that they got the attention they deserved. It is a strange reverse problem in the security world - issues only get treated seriously when they are reported by security people through a formal vulnerability reporting and disclosure program (or informally via full-disclosure and other lists/forums). While Google and other companies take security reports through these formal channels very seriously, I doubt they have anybody dedicated to trawling through user feedback and forums and spotting anything that might be infosec related.