but i'll need to natively incorporate it still.
|11 months ago|
|config||11 months ago|
|dh||11 months ago|
|moduli||11 months ago|
|sharedconsts||2 years ago|
|sshkeys||2 years ago|
|utils||11 months ago|
|.gitignore||2 years ago|
|LICENSE||2 years ago|
|README.md||11 months ago|
|TODO||2 years ago|
|go.mod||11 months ago|
|go.sum||11 months ago|
Compared to something like
rsh, SSH (Secure SHell) is a vast step ahead in terms of security. Since its birth, it's seen
functionality increase by leaps and bounds.
OpenSSH, by far the most deployed SSH implementation, pays special attention to security. However, due to:
- making various compromises for ease of use
- unexpected vulnerabilities (are there ever any expected vulnerabilities?) such as Logjam
- those deploying SSH not being cryptographic experts
- the NSA making a concerted effort to compromise OpenSSH
the default configuration and keys used may not be the strongest they can be (and in some cases, user configuration can be downright dangerous to security).
This software will harden your OpenSSH security as much as possible to currently known weaknesses.
This program will generate/modify and replace:
- Your hostkeys (typically
- The client keys (
~/.ssh/id_*) for the running user
sshd(server) configuration (typically
- Your system-wide
ssh(client) configuration (typically
ssh(client) configuration for the running user (
- The SSH DH parameters (typically
with much stronger implementations from typical/upstream defaults.
Any and all pre-existing files are backed up before being replaced.
It takes the recommendations from Secure Secure Shell (and perhaps other sources) and automatically applies them.
Additionally, it anonymizes your key. It uses a comment string by default that provides no identifying information other than the fact that you are using SSHSecure.
It will create backups of any file(s) it replaces and automatically rolls back
configuration changes if it does not pass the syntax check (
sshd -t) to avoid
accidentally locking you out.
Why a binary?
I originally wrote this as a Python script. However, some machines don't have the Python interpreter installed and due to the lack of low-level access, I ended up making a lot of calls to the shell anyways.
I wrote it in Golang because:
- The source would be easily read for auditing purposes
- Golang is, admittedly, incredibly faster at some tasks than Python
- Multiprocessing/multithreading is incredibly more simple in Golang than Python
- Building widely-deployable binaries is easier in Golang than C or C++
As much as I like Python, Golang should offer significant improvements.
How can I contact you?
You can either file a bug
or email me at
bts [at] square-r00t (dot) net.
Is there anything from the Secure Secure Shell document that you don't implement?
Yep. No TOR hidden service ("Traffic analysis resistance"). The system should be
sufficiently hardened to prevent you from scans yielding anything useful except noisy
logs, and there's much better options for handling those than running SSH over TOR. It
isn't the silver bullet you may think it is. You are,
of course, welcome to turn it up yourself but it is advisable to not run SSHSecure in an
automated fashion in this case as it may revert the changes your
try not to, but it may.