New answers tagged

0

Have you looked at the documentation? There is a LogLevel QUIET|FATAL|ERROR|INFO which defaults to info. LogLevel ERROR turned off these spammy login messages.


0

Thanks to @Jakuje I checked the group membership with groups baz which showed that the effective group is not what I expecting from the entry in /etc/group. As we also have centrify installed, I looked at the config, which seems correct(baz was listed in /etc/centrifydc/groups.ignore). I restarted the agent (service centrifydc restart), which fixed the ...


0

Another solution to this, which doesn't require moving from sshd.socket to sshd.service, is to start tmux server as a systemd service [0]. This way, the tmux server is already running when you SSH into the server, instead of spawned by the tmux command in SSH, thus won't be killed. [0] https://wiki.archlinux.org/index.php/tmux#Autostart_with_systemd


1

Run: sudo systemctl enable sshd.socket To enable service to run on boot.


0

I had the same issue in Fedora 21, I finally zeroed out the Listening Address,ListenAddress 0.0.0.0 and now when they system reboots I am able to SSH without logging into the system first.


2

Does /temp really exist (didn't you mean /tmp)? If it doesn't then your script tries to cd to /temp, fails, and then all the commands run in the starting directory. The last two commands are particularly dangerous because you cd to /, then cd to /temp (which may not exist) and then rm everything (which could well be the root filesystem). You should ...


1

In my opinion you should never ever disable the root user entirely. If you do not want to be able to login as root using ssh you should set the directive PermitRootLogin no in /etc/ssh/sshd_config. For other applications there are mostly equivalent settings which can be made.


0

I found the answer with the help of a very good friend who was very patient with my problem. The problem was that the putty client was not set up to accept my key, I had the authorized key files and all the permissions right it's just that this one little problem was not noticed until now. In my putty client I did not put in a private key into my secession ...



Top 50 recent answers are included