Patched OpenSSH that logs passwords or sends them to a REST api
$ docker run -t -i -p 2222:2222 dougefresh/sshd-passwd-pot sshd -d
$ ssh -l hacker -p 2222 localhost{ "time": 1522258349538, "user": "hacker", "passwd": "password", "remoteAddr": "172.17.0.1", "remotePort": 52708, "remoteName": "172.17.0.1", "remoteVersion": "SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4", "application": "OpenSSH_7.7p1", "protocol": "ssh" }
Could not get shadow information for NOUSER
Failed password for invalid user hacker from 172.17.0.1 port 52708 ssh2
debug1: userauth-request for user hacker service ssh-connection method password [preauth]
debug1: attempt 5 failures 4 [preauth]
{ "time": 1522258351748, "user": "hacker", "passwd": "hacker", "remoteAddr": "172.17.0.1", "remotePort": 52708, "remoteName": "172.17.0.1", "remoteVersion": "SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4", "application": "OpenSSH_7.7p1", "protocol": "ssh" }
Failed password for invalid user hacker from 172.17.0.1 port 52708 ssh2
debug1: userauth-request for user hacker service ssh-connection method password [preauth]
debug1: attempt 6 failures 5 [preauth]
{ "time": 1522258356303, "user": "hacker", "passwd": "password1", "remoteAddr": "172.17.0.1", "remotePort": 52708, "remoteName": "172.17.0.1", "remoteVersion": "SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4", "application": "OpenSSH_7.7p1", "protocol": "ssh" }$ ./docker-build.sh
$ docker build . -t sshd-passwdpot
SSHD_OPTS
You can pass any valid OpenSSH options
docker run -e SSHD_OPTS="-o Audit=no" -t -i -p 2222:2222 dougefresh/sshd-passwd-potRSYSLOG_SERVER
The container is running rsyslogd and will forward messages to 172.17.0.1 by default
You can enable your host's rsyslog to accept messages with
module(load="imtcp")
input(type="imtcp" port="514" address="172.17.0.1")'
echo -e 'module(load="imtcp")\ninput(type="imtcp" port="514" address="172.17.0.1")' > /etc/rsyslog.d/99_listen.confAddressFamily any
AllowAgentForwarding no
AllowTcpForwarding no
Audit yes
AuthorizedKeysFile .ssh/authorized_keys
ListenAddress 0.0.0.0
LogLevel INFO
MaxAuthTries 50
MaxSessions 0
PermitEmptyPasswords no
PermitRootLogin no
PermitTTY no
PermitUserEnvironment no
Port 2222
PrintMotd no
StrictModes no
SyslogFacility local7
TCPKeepAlive no
UseDNS yes
X11Forwarding no
X11UseLocalhost no
Audit yes will log username/password to syslog
Audit [yes|no]
AuditUrl will POST json to url
AuditUrl http://localhost
AuditSocket will POST json to this socket file. AuditUrl must be specified
AuditSocket /var/run/passwd.socket
All PRs are welcome
- Douglas Chimento - dougEfresh
OpenSSH is a complete implementation of the SSH protocol (version 2) for secure remote login, command execution and file transfer. It includes a client ssh and server sshd, file transfer utilities scp and sftp as well as tools for key generation (ssh-keygen), run-time key storage (ssh-agent) and a number of supporting programs.
This is a port of OpenBSD's OpenSSH to most Unix-like operating systems, including Linux, OS X and Cygwin. Portable OpenSSH polyfills OpenBSD APIs that are not available elsewhere, adds sshd sandboxing for more operating systems and includes support for OS-native authentication and auditing (e.g. using PAM).
The official documentation for OpenSSH are the man pages for each tool:
Stable release tarballs are available from a number of download mirrors. We recommend the use of a stable release for most users. Please read the release notes for details of recent changes and potential incompatibilities.
Portable OpenSSH is built using autoconf and make. It requires a working C compiler, standard library and headers, and zlib. libcrypto from either LibreSSL or OpenSSL may also be used, but OpenSSH may be built without it supporting a subset of crypto algorithms.
FIDO security token support need libfido2 and its dependencies. Also, certain platforms and build-time options may require additional dependencies, see README.platform for details.
Releases include a pre-built copy of the configure script and may be built using:
tar zxvf openssh-X.YpZ.tar.gz
cd openssh
./configure # [options]
make && make tests
See the Build-time Customisation section below for configure options. If you plan on installing OpenSSH to your system, then you will usually want to specify destination paths.
If building from git, you'll need autoconf installed to build the configure script. The following commands will check out and build portable OpenSSH from git:
git clone https://github.com/openssh/openssh-portable # or https://anongit.mindrot.org/openssh.git
cd openssh-portable
autoreconf
./configure
make && make tests
There are many build-time customisation options available. All Autoconf destination path flags (e.g. --prefix) are supported (and are usually required if you want to install OpenSSH).
For a full list of available flags, run configure --help but a few of the more frequently-used ones are described below. Some of these flags will require additional libraries and/or headers be installed.
| Flag | Meaning |
|---|---|
--with-pam |
Enable PAM support. OpenPAM, Linux PAM and Solaris PAM are supported. |
--with-libedit |
Enable libedit support for sftp. |
--with-kerberos5 |
Enable Kerberos/GSSAPI support. Both Heimdal and MIT Kerberos implementations are supported. |
--with-selinux |
Enable SELinux support. |
--with-security-key-builtin |
Include built-in support for U2F/FIDO2 security keys. This requires libfido2 be installed. |
Portable OpenSSH development is discussed on the openssh-unix-dev mailing list (archive mirror). Bugs and feature requests are tracked on our Bugzilla.
Non-security bugs may be reported to the developers via Bugzilla or via the mailing list above. Security bugs should be reported to openssh@openssh.com.
openssh/V_8_0