From: Benjamin Stillman Date: June 25 2012 3:59pm Subject: RE: Question about testing memcmp() List-Archive: http://lists.mysql.com/mysql/227740 Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable By recent security breach, do you mean the issue with passwords? If so: htt= p://www.dbasquare.com/2012/06/11/a-security-flaw-in-mysql-authentication-is= -your-system-vulnerable/ for i in `seq 1 2000`; do mysql -u USERNAME --password=3DINCORRECTPASSWORD = -h HOSTNAME ; done If you get in using that, you're vulnerable. But as Harald said, why not just update? Always better to be patched and up= -to-date. Ben Stillman bstillman@stripped -----Original Message----- From: Sabika Makhdoom [mailto:sabika.makhdoom@stripped] Sent: Monday, June 25, 2012 12:17 AM To: mysql@stripped Subject: Question about testing memcmp() I want to test our memcmp() binaries to see if we have the mysql binaries t= hat are impacted by the recent security breach. How do I test it? Thanks Life was meant to be mobile -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql ________________________________ Notice: This communication may contain privileged and/or confidential infor= mation. If you are not the intended recipient, please notify the sender by = email, and immediately delete the message and any attachments without copyi= ng or disclosing them. LBI may, for any reason, intercept, access, use, and= disclose any information that is communicated by or through, or which is s= tored on, its networks, applications, services, and devices.