[3869] in WWW Security List Archive
Re: Netscape eggs -Reply
daemon@ATHENA.MIT.EDU (Gene Ingram)
Fri Dec 20 21:46:51 1996
Date: Fri, 20 Dec 1996 16:22:42 -0800
From: Gene Ingram <gene@hpfsvr01.cup.hp.com>
Reply-To: www-security@ns2.rutgers.edu
To: DAVE SANDERS <DSANDERS@fusn.com>
Cc: steve_neruda@nationwide.com, alan@ctrl-alt-del.com, nichol@maths.ox.ac.uk,
www-security@ns2.rutgers.edu, hmcneill@tssc.co.nz
Errors-To: owner-www-security@ns2.rutgers.edu
Looks like the Netscape eggs might cause problems afterall.
Up to invoking the egg that causes the bright green dragon to
jump out and breath fire from the Netscape logo, my secure server
connection worked fine. I was able to do U.S. secure transactions
at Wells Fargo Bank.
After invoking the Netscape egg, the secure server would take
forever to connect to Wells Fargo, then an error "Socket I/O
Error" would occur. I couldn't even download the latest Netscape
U.S. secure unix version, as the same thing would happen.
I had a feeling the culprit was a rogue egg, so I closed Netscape
and reopened it. The fire breathing dragon is gone... and I can
immediately connect to Wells Fargo and Netscape! There must be
a programmer bug in one of the eggs you sent (as I invoked them
all, so can't conclusively blame the fire breathing dragon egg).
--
___
| ._ _ ._ _.._ _ ``I do not fear computers
_|_| |(_|| (_|| | | I fear lack of them.'' -Isaac Asimov
_____ _| _______________________________________________________
Key fingerprint: 93 E1 15 E6 35 BC B2 84 B2 7B 39 76 29 72 32 72
[Signature lettering created by ``Figlet Ascii Font Converter''
http://mediacube.datacom.de/cgi-bin/moniteurs/figlet]
