On Sat, Feb 16, 2019 at 12:49:07PM +0100, Andreas Kusalananda K?h?ri wrote: > In ssh_config(5): > > ~/.ssh/config > This is the per-user configuration file. The format of this file > is described above. This file is used by the SSH client. > Because of the potential for abuse, this file must have strict > permissions: read/write for the user, and not accessible by > others. > > "not accessible" > > In ssh(1): > > ~/.ssh/config > This is the per-user configuration file. The file format and > configuration options are described in ssh_config(5). Because of > the potential for abuse, this file must have strict permissions: > read/write for the user, and not writable by others. > > "not writable" > > > It would be better (IMHO) to mention explicit permissions, e.g. 600 (but > only if this is what the actual code of ssh is checking for, obviously). > > Also, not being accessible could be seen as a consequence of ~/.ssh not > being accessible, which, if one disregarded the ssh(1) manual, could > possibly be interpreted as meaning having the file writable by others is > okay. > > In any case, they should probably say the same thing. > > -- > Andreas Kusalananda K??h??ri, > National Bioinformatics Infrastructure Sweden (NBIS), > Uppsala University, Sweden. >
morning. the description "not writable" got updated in ssh.1, but looks like we overlooked ssh_config.5. i've just bumped it to read the same/ thanks, jmc
