| Summary: | Add ability to have a ~/.ssh/config.d directory with smaller configs | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Hugh Davenport <hugh> |
| Component: | ssh | Assignee: | Assigned to nobody <unassigned-bugs> |
| Status: | CLOSED FIXED | ||
| Severity: | enhancement | CC: | azmeuk, djm |
| Priority: | P5 | ||
| Version: | 6.2p1 | ||
| Hardware: | Other | ||
| OS: | Linux | ||
This would be great to have the same feature for sshd too. You can achieve this via the ssh_config Include directive closing resolved bugs as of 8.6p1 release |
I've seen forum posts about doing this as a hack in bash to allow it, but was wondering whether it would be supported as a core feature. The use case is like this. I have several different environments, say prod/test/work2/work3/home/otherhome, and they all require entries in ~/.ssh/config, but they are independant of each other. I may share parts of that config, but it would be easier if they were all seperate files in a directory such as ~/.ssh/config.d/{prod,test,work2,work3,home,otherhome} etc, then I can just share the individual files. I understand there may be a problem with ordering, so I would suggest that the ~/.ssh/config is loaded first, and if there is something in there (like an include(dir) directive), then loads the config.d (or other specified directory) in directory listing order. Does this seem like a reasonable feature, I would be happy to help with development if it gets the OK from core devs that it is likely to be integrated. Cheers, Hugh