Tag Info

New answers tagged

0

If the user does not have root access (or any way to gain it, such as exploiting an insecure setuid program), escaping a chroot jail should be impossible. With root access, escaping a chroot jail is trivial. In fact, the chroot(2) manpage even gives instructions: This call does not change the current working directory, so that after the call '.' can ...


0

No it cannot, it would give them an error. That's the whole point of chroot. They'll be only locked up in a location without being able to go out that location. But if you want tias.


2

This is simply a feature of the Cisso ssh server implementation; it parses the user name, and if it contains a :[0-9]+ component then it understands it has to connect the session to the console port with the corresponding number. Note it has nothing to do with an alternate port number, those connects happen over port 22.


0

What do the log say? Connection established. followed by ssh_exchange_identification: Connection closed by remote host means the connection between the client and the server was established but ssh couldn't start. In my humble experience this is often caused by whether TCP_wrapper blocking SSH: check that the rules in the files /etc/hosts.{allow,deny} on ...


0

I figured it out and its completely stupid. My %$&!&**! !%*# terminal session window was bugged! Yes! bugged! Everything was working fine with it except SSH not printing the remote output. I had tried everything else! So I figured what the hell lets start a new term... never thought it would actually fix anything. Curse you xfce4-terminal ...


0

They both store a "RSA key pair for version 2 of the SSH protocol" and can be converted interchangeably however regarding the actual stored format difference: from http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/key-formats-natively.html The advantages of the PuTTY key format are: Public half of key is stored in plaintext. OpenSSH's private ...


0

OpenVPN allows IP routing which doesn't care about users. So there is no need to have two tunnels between the same systems.


1

Use: AllowUsers git peter@192.168.2.* or for example: AllowUsers git peter@192.168.2.2?? if only 200-254 are allocated for VPN connections. And make sure to read man ssh_config (the section PATTERNS). Yes, that's ssh_config, not sshd_config. But if you read the latter, you'll notice it refers to the former.



Top 50 recent answers are included