| 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
| ||
|
Date: Sun, 5 Sep 2010 00:44:53 +0000 From: Harry Strongburg <harry.fd@...ry.lu> To: full-disclosure@...ts.grok.org.uk Subject: Re: reCaptcha secret key - where is the point? On Sat, Sep 04, 2010 at 11:38:38PM +0200, BlackHawk wrote: > Reading here & there i found lot of people scared about they "secret > key" of reCaptcha coud be publically discovered; > But, at this moment, is kind of useless for an attacker, right? or at > least until we find out how the reCaptcha response is calculated.. It just adds more "trust" between the site running the CAPTCHA and Google. It's sent in plaintext to the reCAPTCHA server, anyways. Quoting reCAPTCHA Supprt (http://groups.google.com/group/recaptcha/msg/bd79e6a0efadad51): >The security of reCAPTCHA does not rely on the private key staying >private. We mostly do this to discourage the sharing of accounts. >Please note that we use the referrer to prevent people from hosting >your key on their site. So as far as I can tell, Google/reCAPTCHA only require you get a private key to "lock you in" to it. According to that post, there's no major risk if someone else has your private key, but it should stay - as the name implies - "private". _______________________________________________ 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