ssh:distribute_public_keys
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
ssh:distribute_public_keys [2016/12/05 15:34] – peter | ssh:distribute_public_keys [2019/12/04 21:23] (current) – removed peter | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== SSH - Distribute public keys ====== | ||
- | |||
- | For a bunch of networked servers, I'd rather recommend one of the two following approaches: | ||
- | |||
- | - Store SSH keys in LDAP (OpenSSH servers generally will require LPK patch set). | ||
- | - Provide CA signed certificates to your users and keep a certificate revocation list to centrally disable certain certificates. | ||
- | |||
- | ===== Using generic configuration management software ===== | ||
- | |||
- | Any generic configuration management software like [[http:// | ||
- | |||
- | [[http:// | ||
- | |||
- | [[http:// | ||
- | |||
- | |||
- | ===== Using cron ===== | ||
- | |||
- | Since the **authorized_keys** file is not that complicated, | ||
- | |||
- | You have the " | ||
- | |||
- | Let the " | ||
- | |||
- | |||
- | ===== Using a bash script ===== | ||
- | |||
- | A very easy solution, that does the same with firewall-rules | ||
- | |||
- | Example file hosts.conf: | ||
- | |||
- | <file bash hosts.conf> | ||
- | 192.168.0.1 | ||
- | 192.168.2.99 | ||
- | 192.168.2.100 | ||
- | </ | ||
- | |||
- | |||
- | <file bash distribute.sh> | ||
- | #!/bin/bash | ||
- | for d in `cat ./ | ||
- | echo " | ||
- | scp / | ||
- | done; | ||
- | </ | ||
ssh/distribute_public_keys.1480952047.txt.gz · Last modified: 2020/07/15 09:30 (external edit)