I just upgraded to R5F1. Now, when I try to SSH from another box on my network, I can connect, but when I try to login as root, my password keeps failing.

If I log locally to my myth box as root, the same password works. I don't know what could be happening here.

_________________
Currently running: R5.5, HD5000 x 2, PVR150, Athlon 64 3000+, Chaintech VNF4, 1GB RAM, 2 x 250GB in LVM, MSI NX6200TC -> AA 9A60 -> HDTV

It is set that way purposely in R5F1.

You can log in as another account and SU if you need root access.


From "The Guide"

_________________
Increasing my couch potatoness by a factor of pie.

OK, I understand the security benefits of enforcing that. I just didn't realize it was implemented.

Is there a place to change this default?

_________________
Currently running: R5.5, HD5000 x 2, PVR150, Athlon 64 3000+, Chaintech VNF4, 1GB RAM, 2 x 250GB in LVM, MSI NX6200TC -> AA 9A60 -> HDTV

It is set that way purposely in R5F1.

You can log in as another account and SU if you need root access.


From "The Guide"

_________________
Increasing my couch potatoness by a factor of pie.

It's generally a good idea to provide a link to the R5F1 hints. That way at least some folks take the clue and read the rest of it...

Yup

The Guide

_________________
Increasing my couch potatoness by a factor of pie.

Previously, I used a script that would use id_rsa.pub from the master backend server user mythtv put into authorized_keys of mythtv on my slave backend server.

The key-gen -t rsa i created was a a blank password. this allowed me to issue the command ssh mythtv@mythtvslave /etc/init.d/mythtv-backend start
from the master backend.

I used this command at the end of /etc/init.d/bootmisc.sh to automatically restart the tuners on the slaves after a master reboot and after a mythbackup.

This was extremely useful.

I would like a secure way to do this.

Any ideas.

I could do it as another user but the sudoers stuff is confusing to me right now.
Also, wouldn't this be a very useful feature for others with a slave setup?

I will try to undo the changes listed above, but maybe that isn't the best longtime solution

Undoing the change is literally a matter of deleting or commenting out one very obvious line in the file noted, and restarting sshd. It's not rocket science.