[35093] in bugtraq
Re: LinkSys WRT54G administration page availble to WAN
daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Tue Jun 1 18:00:59 2004
Message-Id: <200406011909.i51J94cX003880@turing-police.cc.vt.edu>
To: steffen.mueller@vision-it.de
Cc: bugtraq@securityfocus.com
In-Reply-To: Your message of "Tue, 01 Jun 2004 16:43:05 +0200."
<200406011643.15877.steffen.mueller@vision-it.de>
From: Valdis.Kletnieks@vt.edu
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_492261736P";
micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 01 Jun 2004 15:09:04 -0400
--==_Exmh_492261736P
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
On Tue, 01 Jun 2004 16:43:05 +0200, Steffen Mueller <steffen.mueller@visi=
on-it.de> said:
> did you check the alternative firmwares available for the Linksys ?
> =
> Great enhancements are available from SVEASOFT. =
> =
> http://www.sveasoft.com/modules/phpBB2/index.php
I haven't looked, but all the same, it's probably insanely great.
The problem is that 95% of the people that buy a Linksys couldn't figure =
out
how to jump through all the hoops to install it.
Sure, Alan can install it. And probably a few dozen others on the list w=
ill be
motivated to do the firmware upgrade. However, if Linksys sold 5 million=
of
these critters, that leaves 4,999,950 or so with lame defaults....
Consider another example - it's *quite* possible to nail down a Windows b=
ox to
drastically tighten the security on it. Why do we still have problems? B=
ecause
it isn't that way "out of the box", and users can't/won't do it after unb=
oxing
it....
--==_Exmh_492261736P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001
iD8DBQFAvNRQcC3lWbTT17ARAmJDAKCA/ke23BBdHFE25FhixTC52e74+gCgs6mo
+vYnTA604tNw2GPV+WWY0jg=
=ZcZf
-----END PGP SIGNATURE-----
--==_Exmh_492261736P--
