[170786] in North American Network Operators' Group
Re: Serious bug in ubiquitous OpenSSL library: "Heartbleed"
daemon@ATHENA.MIT.EDU (Patrick W. Gilmore)
Wed Apr 9 11:32:33 2014
From: "Patrick W. Gilmore" <patrick@ianai.net>
In-Reply-To: <5345668C.30807@flowtools.net>
Date: Wed, 9 Apr 2014 11:31:48 -0400
To: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--Apple-Mail=_924DA569-0CBA-4C44-A38F-6B40B7C6FBDB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=iso-8859-1
On Apr 09, 2014, at 11:26 , Me <jschiel@flowtools.net> wrote:
> On 04/08/2014 09:46 PM, Rob Seastrom wrote:
>> If that's true, you might want to consider immediately disconnecting
>> your systems from the Internet and never re-connecting them. After
>> all, theres a lot of online unseen code testing your site already
>> whether you like it or not.
>>=20
>> -r
>>=20
> Sending someone to a site with obscure TLDs of .io or .lv doesn't help =
in these situations. This is a perfect opportunity for someone to set up =
a drive by site to drop malware on someone's computer.
>=20
> I'm not saying these sites did that but in order to see the code, =
someone would have to visit the site first. I personally would use wget =
instead of a browser for sites like these and did so in this situation.
>=20
> And yes, your point is not lost on me, there are tons of sites that =
have obfuscated code and malware running on them, I know that.
In the list of tools were several sites with code you could download, =
review, and run locally on your machine to test against the bug.
However, I trust some of the sites listed. My new favorite is =
<https://sslanalyzer.comodoca.com/>, since it takes ports other than 443 =
and gives back a lot of info.
--=20
TTFN,
patrick
--Apple-Mail=_924DA569-0CBA-4C44-A38F-6B40B7C6FBDB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJTRWfkAAoJEHZX8udmu5TX69AH/28jPRPWVywM88zY/PFmRIn8
Ai8EQ3i6dx0KSvWeO2WosCKzIBu7UyZuRC4gVcNbDqmjJgYWst0M9QcZikI5+UQH
t6ZXX+N3VfAeinltPaoNs1RskHLNk9HDCPCinTo0Srqj3n6f9kg/j7N04pnZTSc1
EvX0t0zELnvz/2fW3RVSlEjLUdPMQJk61+EaDxsk5v8XA4z7L0URWmBZxQYrGb48
88byp2VF6oUDBv+/pSkQqneVSPmJea/4C3HpwdcSUyZVK+POPUAHoQ9yf/bB6obH
LAs6Sx5nwNhil0+gQ3jlxyBk0gvUZr8I+1w6zDpDDrJuY5eTEfqXQXa17YkA5ck=
=ZR3S
-----END PGP SIGNATURE-----
--Apple-Mail=_924DA569-0CBA-4C44-A38F-6B40B7C6FBDB--
