Global SSH client configuration, ssh_config(5), at scale
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Global SSH client configuration, ssh_config(5), at scale
I am now wondering about what kind of use-cases are out there for pushing out a modified SSH client configuration file using orchestration software.
Any descriptions of such use cases for modifying the global client configuration, no matter how vague, will be gratefully received.
Note, I am wondering only about the client ssh configuration, which would be the one normally found in /etc/ssh/ssh_config on most systems, and not for the server daemon's configuration which would be /etc/ssh/sshd_config.
I don't know of a good reason. As far as I know the command line settings can override the user settings (~/.ssh/config) which can override the system settings (/etc/ssh/ssh_config).
As far as I know the command line settings can override the user settings (~/.ssh/config) which can override the system settings (/etc/ssh/ssh_config).
Yes, that's the priority. I don't know of a good reason either which is why I am now wondering, but I figure there must be some site-wide settings that institutions like to use.
There are wonderful mass management utilities for enterprise operations such as puppet.
Also, you CAN roll your own and we did before things like puppet became finished and general. I do not recommend rolling your own, rather evaluate existing options. These will allow you to manage much more than just the ssh client, so if that is ALL you need a roll-your-own solution might be better.
There are wonderful mass management utilities for enterprise operations such as puppet.
Also, you CAN roll your own and we did before things like puppet became finished and general. I do not recommend rolling your own, rather evaluate existing options. These will allow you to manage much more than just the ssh client, so if that is ALL you need a roll-your-own solution might be better.
Yes, there are a lot of orchestration tools out there, some quite good. However, rather than which tools to use for orchestration, my question is about what kind of actual content can be pushed in the context of the SSH client's system-wide configuration file, /etc/ssh/ssh_config.
Yes, there are a lot of orchestration tools out there, some quite good. However, rather than which tools to use for orchestration, my question is about what kind of actual content can be pushed in the context of the SSH client's system-wide configuration file, /etc/ssh/ssh_config.
If you believe the proponents of those software packages there is almost nothing they CANNOT change! I have not used them enough to testify to that, but this is something pretty basic. That is a simple text file for configuration, and requires only superuser authority to change. Simple, if you start as the administrator of each system.
One reason for distributing a common client cfg would be if your company uses a bastion or 'jump' servers ie you do not allow direct cxns to your actual servers. https://www.redhat.com/sysadmin/ssh-...tion-proxyjump
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.