[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <037001cd36c6$5a0edb40$0e2c91c0$@emitcode.com>
Date: Sun, 20 May 2012 13:22:58 -0700
From: "Michael J. Gray" <mgray@...tcode.com>
To: "'Jann Horn'" <jannhorn@...glemail.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Google Accounts Security Vulnerability
That was a bit ambiguous and I apologize for that. I meant that I had
reproduced the issue several times, not created test accounts. I'm willing
to bet it's not just a few accounts being affected.
-----Original Message-----
From: Jann Horn [mailto:jannhorn@...glemail.com]
Sent: Sunday, May 20, 2012 4:39 AM
To: Michael J. Gray
Cc: 'Thor (Hammer of God)'; 'Dan Kaminsky';
full-disclosure@...ts.grok.org.uk
Subject: Re: [Full-disclosure] Google Accounts Security Vulnerability
On Sat, May 19, 2012 at 12:04:43PM -0700, Michael J. Gray wrote:
> On why I don't want to provide my email address to Google:
>
> It's a different email address which I don't want associated with this
> email address for various reasons. That is why I am not going to provide
it.
>
> Your assumption that it's a simple piece of information and requires
> no effort to give out is correct, but the impact of the association is
> unwanted.
Sounds reasonable.
> The fact that Google can create a test account and reproduce the issue
> (as I have now done several times) tells me that they want the account
> information for some other purpose or that they're just being lazy.
So, you now have a test account that doesn't reveal any secrets about you
and which is affected... so you could surely give Google the name of that
one?
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists