Issue #1737 has been updated by jamtur01.

Status changed from Unreviewed to Closed
Target version set to 0.24.7

Pushed in commit:"e032034fc4f5f45d883f24104c436e16ce555c0e" in branch 0.24.x
----------------------------------------
Bug #1737: ssh_autorized_key cannot parse lines with a command containing a 
comma
http://projects.reductivelabs.com/issues/show/1737

Author: thias
Status: Closed
Priority: Normal
Assigned to: 
Category: ssh
Target version: 0.24.7
Complexity: Unknown
Affected version: 0.24.6
Keywords: 


I'm seeing a problem similar to the one in ticket #1417 but with commas "," 
instead of spaces " ".

Using ssh_authorized_key, I'm passing the option @from="host1,host2"@ and when 
doing that, puppet thinks the options have changed at each run, and updates the 
@~/.ssh/authorized_keys@ files every time. Not a huge blocker, but it's filling 
up the logs with useless entries.

Example log entry that is seen every run :
<pre>
Fri Nov 07 10:24:59 +0100 2008 
//Node[foo]/bar-server/Bogus-user[bogus]/user-bogus/Ssh_authorized_key[bogus]/options
 (notice): options changed 
'from="host1host2"no-port-forwardingno-agent-forwardingno-X11-forwardingno-pty' 
to 'from="host1,host2" no-port-forwarding no-agent-forwarding no-X11-forwarding 
no-pty'
</pre>

When I change the @from=""@ option to contain a single host, hence without any 
comma, then all works fine. This is using puppet 0.24.6.


----------------------------------------
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to