Disclosure timeline for vulnerabilities under active attack

Re:Disclosure timeline for vulnerabilities under active attack by benmanns on Thursday May 30, 2013 @12:17PM (#5793373)

Agreed. I don't think there is anything stopping me from registering googleinternetsecurity.blogspot.com or officialonlinesecurity.blogspot.com if they filter out "google."

[ Parent | on HN ]

Re:Disclosure timeline for vulnerabilities under active attack by CGamesPlay on Thursday May 30, 2013 @12:31PM (#5793461)

Nor googleinternetsecurity.com. A TLD doesn't make it more legit, but at least under Blogspot, Google can shut down an imposter once discovered.

[ Parent | on HN ]

Re:Disclosure timeline for vulnerabilities under active attack by packetslave on Thursday May 30, 2013 @12:35PM (#5793490)

The Google security folks have been getting more and more selective about what goes under google.com (especially user-generated content) because stealing google.com cookies gives you the user's auth tokens.

[ Parent | on HN ]

Re:Disclosure timeline for vulnerabilities under active attack by TeMPOraL on Thursday May 30, 2013 @12:33PM (#5793477)

How about internetsecurity.google.com? They control their own TLD, they can make subdomains.

[ Parent | on HN ]

Re:Disclosure timeline for vulnerabilities under active attack by jcrites on Thursday May 30, 2013 @10:41PM (#5796565)

I think you mean they control a second-level domain. The top level domain is "com" in the example of "internetsecurity.google.com".

http://en.wikipedia.org/wiki/Top-level_domain

[ Parent | on HN ]

Re:Disclosure timeline for vulnerabilities under active attack by TeMPOraL on Saturday June 01, 2013 @04:13PM (#5805770)

Yes, that was what I meant :).

[ Parent | on HN ]

Re:Disclosure timeline for vulnerabilities under active attack by mixedbit on Thursday May 30, 2013 @05:21PM (#5795326)

internetsecurity.google.com could set cookies on google.com

[ Parent | on HN ]