From: Reindl Harald
Date: June 25 2012 9:16am
Subject: Re: Question about testing memcmp()
List-Archive: http://lists.mysql.com/mysql/227737
Message-Id: <4FE82C59.2020402@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigB123F5A6363CB792249876A1"

--------------enigB123F5A6363CB792249876A1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Am 25.06.2012 06:17, schrieb Sabika Makhdoom:
> I want to test our memcmp() binaries to see if we have the mysql binari=
es that are impacted by the recent security breach. How do I test it?

why do you simply not update?


--------------enigB123F5A6363CB792249876A1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/oLFkACgkQhmBjz394AnkCqwCfey224Oq/ExfJHZ8zs0lUNYnV
YtUAnimCRWtQAZG+1IGLMhmYJWpPE/eP
=X89j
-----END PGP SIGNATURE-----

--------------enigB123F5A6363CB792249876A1--