leap_platform.git/puppet/modules/site_sshd/templates, branch 0.6.0 [leap_platform] include a host information in ssh_config for ever possible host a given node might communicate with. this includes port and host key algorithm. closes #6432 2014-11-26T00:25:43+00:00 elijah elijah@riseup.net 2014-11-26T00:25:43+00:00 83267a00f272a6f3f52a66eca44d9ca85924cc8e 






Include check_mk monitor pubkey in /root/.ssh/authorized_keys
2014-02-14T16:38:02+00:00

varac
varacanero@zeromail.org

2014-02-14T16:38:02+00:00

d0eea33d88a6ffcbe01544678372d80e8c8de51f

instead of creating a /root/.ssh/authorized_keys2

see https://review.leap.se/r/148/#comment153





instead of creating a /root/.ssh/authorized_keys2

see https://review.leap.se/r/148/#comment153







turn off StrictHostKeyChecking for vagrant ssh clients
2014-02-10T23:43:39+00:00

elijah
elijah@riseup.net

2014-02-10T23:43:39+00:00

0b3e87cd6916d4ca4404fd2b375d21468d17f343












deploy a valid /etc/ssh/ssh_known_hosts for all nodes (requires new leap_cli)
2014-02-10T01:04:58+00:00

elijah
elijah@riseup.net

2014-02-10T01:04:58+00:00

665db30f37838bcebbfdc368f65ed369282c31b8












switch to own define for managing ssh keys
2013-06-30T16:51:35+00:00

varac
varacanero@zeromail.org

2013-06-27T08:52:54+00:00

6c34c73f7e4c5203321547b699c6eaba9de8e2fe

The problem with puppet's built-in ssh_authorized_key is that you can
purge unmanaged keys in a authorized_keys file. see
https://leap.se/code/issues/3010 for details.

Conflicts:
	puppet/modules/site_sshd/manifests/authorized_keys.pp

Change-Id: I640bf7ebc0f0f7fb19cc46feb4cb2702d6561a9b





The problem with puppet's built-in ssh_authorized_key is that you can
purge unmanaged keys in a authorized_keys file. see
https://leap.se/code/issues/3010 for details.

Conflicts:
	puppet/modules/site_sshd/manifests/authorized_keys.pp

Change-Id: I640bf7ebc0f0f7fb19cc46feb4cb2702d6561a9b