full-disclosure - Re: Google Accounts Security Vulnerability

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120520113914.GB21288@Jann-PC.fritz.box>
Date: Sun, 20 May 2012 13:39:14 +0200
From: Jann Horn <jannhorn@...glemail.com>
To: "Michael J. Gray" <mgray@...tcode.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: 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?

Content of type "application/pgp-signature" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/