Hot answers tagged

2

There are two things that you want to achieve: Disallow the authentication using ~/.ssh/authorized_keys As proposed set AuthorizedKeysFile to some different place. If there is the discussed requirement, it will not be evaluated (otherwise there is nothing more to solve). Set AuthorizedKeysCommand The command will return you the authorized keys from your ...


2

Get a better provider than GoDaddy. BlueHost or Hostgator spring to mind, although I've never used either. Your ps aux output shows that your ssh session is currently using 1.8kib of memory 1.8 SSH 1.6 -bash 124 cpaneld 1.02 ps aux All sizes are in kib, so total is about 128mb. It's not unreasonable to think that a fully configured and running OS ...


1

A simpler approach would be: Just tell your users to add an alias for your git-server to the ~/.ssh/config. Then they have the same convenience as with github and you don't have to do some weird redirections on the server side. For example: # put into ~/.ssh/config Host mygitlab Hostname git.example.org Port 10022 Then your users can just clone etc. ...


1

The rssh manpage indicates it should be the login shell of these users: The system administrator should install the shell on the restricted system. Then the password file entry of any user for whom it is desireable to provide restricted access should be edited, such that their shell is rssh. For example: ...


1

As pointed out by Ulrich Schwarz, .ssh/authorized_keys must be a regular file. In your case, it looks like it's a directory. You need to remove the directory and create a single text file with the key in it.


1

I believe you need is ssh-keygen, which remembers your "device signature". So even you changed your password, it still works as long as you ssh from the same device. Here is a detailed tutorial how to set it up. Does it need to be run in root privilege? No, you only need root privilege on the host-server when you set it up, in order to edit some file ...


1

It was asked before on ServerFault. Quoting with few modification and notes: Start the process with /usr/sbin/sshd -f ~/.ssh/sshd_config where ~/.ssh/sshd_config is a new file you created. Among other options (such as a different host key, different port, etc) you need to add the line UsePrivilegeSeparation no. This will prevent the sshd process from ...



Only top voted, non community-wiki answers of a minimum length are eligible