Skip to content

Commit

Permalink
Merge pull request #34 from TelekomLabs/faq-crypto
Browse files Browse the repository at this point in the history
added info on crypto to readme
  • Loading branch information
chris-rock committed Aug 4, 2014
2 parents a193dce + 19e99e8 commit 74f47c3
Showing 1 changed file with 9 additions and 0 deletions.
9 changes: 9 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,15 @@ The proper way to solve this is to unlock the account (`passwd -u myuser`). If t

Alternatively, if you intend to use PAM, you enabled it via `['ssh']['use_pam'] = true`. PAM will allow locked users to get in with keys.


**Why doesn't my application connect via SSH anymore?**

Always look into log files first and if possible look at the negotation between client and server that is completed when connecting.

We have seen some issues in applications (based on python and ruby) that are due to their use of an outdated crypto set. This collides with this hardening module, which reduced the list of ciphers, message authentication codes (MACs) and key exchange (KEX) algorithms to a more secure selection.

If you find this isn't enough, feel free to activate `['ssh']['cbc_required']` for ciphers, `['ssh']['weak_hmac']` for MACs, and `['ssh']['weak_kex']` for KEX.

## Contributors + Kudos

* Dominik Richter
Expand Down

0 comments on commit 74f47c3

Please sign in to comment.