Debbie Hurley <dhurley@ieaccess.net> hath wroth:
>I believ him when he says I need to upgrade my router.
You don't need a new router. You need a firmware update. No big
deal. What I'm concerned about his how remote access got turned on
and who did it (and why). You might want to interrogate the kid.
>You are the
>only one here who believed me.
Yes, but don't presume it's my good intentions or generous attitude.
The problem is that old bugs tend to come back. One version fixes a
problem, the next version brings it back as sloppy coders recycle old
code. In the software biz, it's part of regression testing.
>I thought I was going crazy when the "experts" were telling me what
>I saw I didn't see.
Chuckle. Ever see any magic tricks or sleight of hand? It looks
real, but you just know something is going on in the background. Well,
hacking and breaking in are like that. I derived considerable
entertainment at the expense of a few IT people (who now hate my guts)
breaking into their systems using social engineering, and then making
it look like some kind of vulnerability or systemic problem. Yeah, I
know I have a warped sense of humor, but it keeps me entertained. The
only problem is that the IT people now hate my guts. Oh well.
Anyway, be careful that what you're seeing is actually a breakin or
vulnerability in progress, and not the residue from a previous
breaking. The fact that remote access was apparently enabled makes me
VERY suspicious.
>I felt like I was being persecuted for reporting this.
Well sure. Blame the victim and all that. Nobody wants to be told
their network is full of holes and vulnerable to attack. Why bother
fixing the problem when you can simply discredit the person that found
the problem?
>I didn't realize that the Linksys WRT54G router I bought was so weak.
It's old firmware. Someone goofed and it's been fixed. All vendors
have their security holes and problems.
>Why didn't Linksys TELL me about this in the package?
Actually, that's a good point because I couldn't find it in the
firmware release notes. It's fashionable to disclose vulnerabilities
only after the fixes are available. That's a fair method, but doesn't
work if users like yourself do not perform ritualistic firmware
version checks and updates.
>I have never updated my
>"firmware" before. Can you hand hold my hands a bit to tell me how to do
>it. I don't want to ruin the router.
There are instructions on the Linksys web site (somewhere). It's
basically very easy. Download the firmware image file. Make an extra
effort to be sure you have the correct version and file. You still
haven't bothered to disclose your WRT54G hardware mutation, so I can't
offer specific advice, filenames, and URL's.
Uncompress the download if it's a ZIP file. Go to the firmware update
page:
<http://www.linksysdata.com/ui/WRT54G/v5/1.00.6/Upgrade.htm>
and browse merrily to the .bin (or whatever) file. Hit update and
wait. When you think it's done, wait some more. Figure on about 2
minutes to be safe. With v5/v6, I don't think you have to reset
anything. That's it.
>BTW, my neighbor said to change my IP address and the hostname and media
>address of my router and pc constantly because that's what he used to
>figure out which was mine in the neighborhood. Is there a way to change the
>router & PC hostname and media name automatically every day or do I have to
>do it manually every day to be safe?
Don't bother. Almost all of that manner of improving security
consists of either obscuring your setup or introducing additional
obstacles. Those are good if you enjoy complicating your own life as
well as that of the prospective hacker, but are generally near
worthless. See the FAQ at:
<http://wireless.wikia.com/wiki/Wi-Fi#Wi-Fi_Security>
Your real security is in:
WPA-PSK or WPA2-PSK encryption
Password for router access
Firmware updates
Most of the tweaks are of marginal value.
If you want real security, setup a VPN and a RADIUS server. The
RADIUS server provides a login and password per user, but also
delivers a unique one time WPA encryption key which cannot be leaked.
If I wanted to attack your system, I would not attack the router, but
would try to extract the WPA key from your Windoze registry. See:
<http://www.wirelessdefence.org/Contents/Aircrack-ng_WinWzcook.htm>
A RADIUS server eliminates the use of a shared key, but preventing it
from being leaked. Ummm... Don't tell the 15 year old brat.
As for your other questions....
>One thing I'd like to do is change the login name!
>I asked on the linksys forums and will check to see if there is a way to
>change the login name from just a dumb blank stare to something interesting
>so others can't get in so easily through the front door of the router.
You can't do that with the stock Linksys firmware. There's only one
user and that's admin. Other routers allow additional users and even
user levels, such as read-only users. If you really want this
feature, the alternative firmware (DD-WRT, OpenWRT) all have
additional users. However, again, this is nothing but security by
obscurity and doesn't provide any real security. Anyway, user names
are suppose to be publicly accessible and not hidden like a password.
Incidentally, one of my accomplices decided that I should test his
system security. He did all the right things, but I still managed to
break in. I tricked him into using his laptop to "test" the security
by claiming my laptop was dead. He stupidly saves all his passwords
in his Firefox browser. It was a simple matter to connect,
automatically login with the saved password, and collect my free
lunch. This is again why I don't like shared keys, stored passwords,
and other convenience features.
>What I don't get is why the Linksys WRT54G router has a password but not a
>login name. Wouldn't it be MORE SECURE if I could change the login name?
Lack of sufficient RAM and NVRAM in the router limits the features
that can be crammed inside. Again, the login name is suppose to be
publicly known and accessible and should not be treated as yet another
password. It also doesn't add much security as the same mechanisms
I've previously listed to bypass passwords will work with login names.
>Am I doing something wrong?
1. You didn't specify WRT54G hardware mutation after being asked by
multiple people for this information.
2. You didn't search with Google to see if it was a known problem.
3. Declared the WRT54G to be worthless BEFORE asking if there was a
fix.
4. Trusted my advice. Don't trust ANYONE about security without
first understanding what you're doing, why it's necessary, and
verifying that it's considered a reasonable thing to do.
5. Posted far too many replies. I'm lazy and don't like hopping from
message to message.
>Likewise with the host name. Why does it have a host name that isn't used
>and why can't I just set the hostname to a blank.
That's been asked before, but with no definitive conclusion. The
current guess is that a hostname is required for syslog to work. It
can be anything, but not blank.
--
Jeff Liebermann
jeffl@cruzio.com
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558