On Sunday 27 November 2016 11:47:39 Mark wrote: > On 11/27/2016 11:02 AM, Gene Heskett wrote: > > On Sunday 27 November 2016 08:12:38 Mark wrote: > >> And that "xhost +" command opens up your machine to the world. If > >> you are going to use native X rather than an encrypted connection > >> through ssh, at least narrow that down by using "xhost + > >> <machine_you_wish_display_to_be_on>". > >> > >> <snipagge> > >> > >>> Cheers Matsche > >> > >> Cheers, > >> Mark > > > > One last detail before I go out to see why ssh'ing into the raspi > > has died. I made the mistake of rebooting it and its pingable but > > refusing connections. So I've undone the sshd_config stuff on the > > rest of the machines, but I'll have to plug console and hdmi cables > > into it to do that in person. > > > > Then the question is, do I have to be logged into the machines for > > this to work, or, can I put this stuff in the rc.local files so its > > just done when I power up the whole thing with one dpst 30 amp > > switch? > > Gene, > > Simply changing the sshd_config shouldn't require a reboot. You > should be able to just restart the ssh server daemon. If it doesn't > come up, it sounds like a typo. You should be able to run 'sshd -T" > to test your config files before restarting to see if there are any > problems before restarting the server daemon. > But I can only do that from its own keyboard, and I've not made it out there yet.
What I was trying to do was to have all this done, either in the correct rc.local files or in a file that I can have auto executed as soon as I am logged in. > Not sure what you mean by having to be logged in though. You can make > the changes, test them, then restart the daemon if successful on the > test. The restart of the daemon will kick you out, but if the test > was successful, you should be able to log back in. The config files > in the /etc/ssh directory are where everything needs to go, > configuration wise. The rc.local files are just startup file with > certain options to be passed to the server daemon as it starts up. > You shouldn't have any configuration parameters there. > > > Waiting for the coffee to kick in. > > > > Thanks Mark. > > > > Cheers, Gene Heskett > > Cheers, > Mark Forgot to send this, but I've been out there, trying to get it to work, but the message on the raspi's screen is that it cannot open 192.168.71.9:0 for use. FWIW, the odroid64 at this time has a full xwindow session running. But I also have another problem on the pi, I am not user 1000. I can copy a script from a forum message that will fix it, but it also leaves me with a skel home directory. Strangely that does not seem to be a problem. So I have rm'd the .Xauthority files, which had grown quite large from all my putzing. But I am going to run that script from rc.local on the raspi so that I have full sudo rights before I try the next thing to check. There must not be anyone logged in when this change my user number to 1000 is ran. Later, after I've fixed me on the raspi. Thanks Mark Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
