Jira (PUP-1177) sshkey creates /etc/ssh/ssh_known_hosts with mode 600

[Felix Frank (JIRA)]

Title: Message Title

Felix Frank commented on an issue   Re: sshkey creates /etc/ssh/ssh_known_hosts with mode 600 Good thinking, but I believe that this goes too far. An existing parsedfile should keep whatever permissions it had before it was rewritten. If we do use replace_file, we commit to one mode that is always enforced. That would make it impossible for users to configure their systems with a non-standard mode for, say, ssh_known_hosts. I feel that it would be much more appropriate to keep using Tempfile, but to go ahead and set its mode to 644 before copying it to the target location. But doing this for all parsedfile providers might be harmful, because some providers might rely on the 0600 default (ssh_authorized_key, I'm looking at you). Add Comment   Puppet / PUP-1177 sshkey creates /etc/ssh/ssh_known_hosts with mode 600 Using the sshkey type /etc/ssh/ssh_known_hosts is created with mode 600 by default. This seems undesirable in most situations. I think the default should be 644. I didn't see anything obvious in the sshkey code that set it strictly on purpose. Does puppet default to 600 somewhere? And is there a simple way to tweak a type to use a different mode? Th... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.