Ciges's questions

I am trying to limit the number of total OpenSSH connections to our Unix systems.

At first, I have tried modifying OpenSSH configuration with MaxSessions and MaxStartups options but with no success. They are ignored (maybe I don't really understand what this options are intended to).

Using PAM limits in /etc/security/limits.conf I have succeed with maxsyslogins directive:

# limit connections to the system to 10
*    -    maxsyslogins    10

It works, but we are limiting all kind of logins to the system, and using a third party solution to apply limitations to OpenSSH. By example, we have different kind of Unix (HP-UX, Solaris, Linux, AIX) and in not every server we are using PAM for authentication.

I mean, does it exists a simpler and more direct way to do it? Something similar to Apache MaxClients directive?

I don't find it and it's very strange for me that OpenSSH does not have this possibility :-|.

I have a curious problem with OpenSSH in SLES 12 SP4 Linux servers.

We install a customized OpenSSH on ourservers, so in each machine we have two versions of OpenSSH, the official package of the operating system and the one that we have compiled.

For the case of SLES 12 SP4 if we run the following command from another server

scp -r directory/. destination_server:/path/to/directory

the following error arises

scp: error: unexpected filename: .

We have verified that the problem is with the scp binary under /usr/bin/scp, which is run by our OpenSSH instead of its scp under its own path.

After searching and testing the solution applied is to remove the execution rights on /usr/bin/scp, so our version of OpenSSH can not use it, and the scp -r from the client works perfectly.

Is there a more elegant to way to tell to the daemon to use the scp binary under its own path instead of /usr/bin/scp?

Best regards