Fixing SamyGO telnet/SSH/SCP/bash on C/D/E/F series

[sectroyer]

Ok, so once for all which files need to be linked to dropbearmulti?
dropbear, scp and dbclient that's it?
What about dropbearkey and dropbearconvert?

You can leave them as they were. Files dropbear, scp and dbclient are used directly for SSH/SCP and therefore need to be replaced since with default ones it doesn't work. That's the reason why without setting everything up it worked for you when you launched dropbear manually. Then samygo already did set up many things needed for SSH/SCP. If you want everything work nice with samygo init scripts it's better to replace this files

[panni]

I'm on F-Series. Do I have to follow the instructions in the first post, or the E series (second post)?

[sectroyer]

I would try the e series way:) but it was not tested on F so you might have to change some things. On H I used E method but also had to make some H specific changes:)

[panni]

Can I substancially break access to my TV when trying the E-Series approach? Or is netcat always possible?

[sectroyer]

Can I substancially break access to my TV when trying the E-Series approach? Or is netcat always possible?

I think net cat should still work. The patch isn't as intrusive to cause so big problems... Worse case scenario you would have to reinstall SamyGO once again so to be sure (because no one tried it yet) just backup all your important data and try

[panni]

Do I still have to do parts of post one? Like adding rcEXT and rc.fix_telnetd? Or just the stuff from the E-Series post? (If so, I don't really get it, as I already seem to have all the stuff like it was mentioned in the E-Series posting, just not the busybox and the dropbearmult part)

- I'm currently just trying to be able to log in via SSH. As I can only run dropbear from web shell I can't let it stay in the foreground to see what's happening (user/pass auth and pubkey auth don't work).


Edit: Getting near:

Code: Select all

root@(none) mnt $ dropbear -E
[3097] Jan 01 00:35:17 Failed reading '/mtd_rwarea/dropbear_dss_host_key', disabling DSS
[3102] Jan 01 00:35:17 Running in background
[3103] Jan 01 00:35:24 Child connection from 192.168.0.67:57695
[3103] Jan 01 00:35:27 user 'root' has invalid shell, rejected
[3103] Jan 01 00:35:30 user 'root' has invalid shell, rejected
[3103] Jan 01 00:35:34 user 'root' has invalid shell, rejected
[3102] Jan 01 00:35:50 premature exit: Terminated by signal
[3103] Jan 01 00:35:50 exit before auth (user 'root', 6 fails): Terminated by signal

This actually worked via web shell.

Edit2: Okay, further in. SSH working now. Used the currently disabled line from rcSGO:

Code: Select all

####harden. mount --bind does not work on F series without SRS_module.ko. Obsolete command now.
#	if [ ! -e /mtd_rwarea/passwd ]; then
#		echo "root:saJvQKUdIxRW2:0:0:SamyGO secured Root:$NEW_HOME:/bin/sh" > /mtd_rwarea/passwd
#	fi

Copied that string to /etc/passwd, set home to /mnt and it magically worked. Though after changing the password it continues to work.

Doesn't somehow work with the current default /mnt/bin/ash shell. I guess because it isn't a default shell and /etc/shells doesn't exist (and doesn't list it naturally).

[sectroyer]

You need SRS_module. And NEVER, NEVER test anything from me trough webshell

[panni]

I had no other option as via telnet I couldn't run stuff requiring stdin/stdout.

The default SamyGO for F-Series does have broken SSH as I see it - SRS_module isn't shipped by default and after changing the shell of root to /bin/sh SSH login works. (I've seen many users reporting SSH not working on F-Series, isn't this the fix?)

[sectroyer]

I had no other option as via telnet I couldn't run stuff requiring stdin/stdout.

The default SamyGO for F-Series does have broken SSH as I see it - SRS_module isn't shipped by default and after changing the shell of root to /bin/sh SSH login works. (I've seen many users reporting SSH not working on F-Series, isn't this the fix?)

First of all. You don't have telnet on your F? This is the E/F fix for the ones that have telnet

[panni]

No, I think we misunderstood each other. My SSH is working now, without your fix and without SRS_module. I've just changed the shell of root in /etc/passwd to /bin/sh (from /mnt/bin/ash) and now the login works.