Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a project where I'll have a number of remote Linux systems in the field. From time to time they'll need to connect to a central server via SSH. These remote systems are automated and have no user present. The number and IP of the remote systems is likely to change often, so keeping a central list of them may be difficult. I am looking at client certificates but they would require an addition to the know_hosts file on the server for each client?

Given this what would be a good way for the single server to authenticate SSH connections from the remote machines?

TY, Fred

share|improve this question
    
Some user will do the ssh connection, be it a cron job, or some other service. you could use public key cryptography, and then you'll have to add an entry for each computer in ~/.ssh/authorized_keys of the user being logged into on the central server. –  Waleed Hamra Nov 19 '12 at 14:35
    
Thanks for the feedback. So with PK each time a new remote node is setup we'd need it to generate it's public key and append that to authorized_keys on the server? –  fred basset Nov 19 '12 at 15:43
    
yup, that's the general idea –  Waleed Hamra Nov 19 '12 at 15:45

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.