NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
felipe_ceglia
Jul 07, 2014Aspirant
RN102 v6.1.8 - cant access SSH
Hello folks, I have a RN 102, now upgraded to 6.1.8. I used to access it via SSH and rsync files from another RN102 to it. Suddenly I cannot access it via SSH anymore. Web interface is ok. I ...
felipe_ceglia
Jul 21, 2014Aspirant
xeltros wrote: Having a shell set to /bin/false is a way to say "sorry guy you don't have the right to login".
Permit root login is required to SSH with the root account. If not enabled you will have to fall back to another authorized ssh account then issuing the "su" command without a login name behind it to go to root mode. That's a security thing to avoid brute force on root account and if "sudo" is not enabled you would have to get passed two password to get root powers which enhances security.
How did they SSH in, did you activate tech support mode (or the SSH section in support in the settings) ?
Yes Netgear "basic tech" are not authorized to use SSH, you would want to escalate for someone to be able to issue commands, but I'm not sure they would do that for a problem that could have been caused by SSH... But if they got in, you may be able to get in too, except if they used some backdoor account.
Regarding /bin/false, yes, you are right. But something changed it, my user account default shell was bash.
I disabled root login for ssh for the very reason you mentioned.
I dont know how they SSHd into the box. I enabled the tech mode thing, I open no NAT port and the guy got in. Seems like they have something that works inside-out.
When I plugged the serial console, I managed to login as root and change my shell back from /bin/false to bash.
cheers,
Felipe
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!