Issue #19994 has been updated by Roger Kennedy.

Status changed from Unreviewed to Closed
Assignee changed from Charlie Sharpsteen to Roger Kennedy

I cannot get this to repro in 3.2.2 or 2.7.18.

The closest version to the reported version in the PuppetLabs Debian repo is 
2.6.18, but I cannot get it to install and run on my Wheezy lab systems.

2.6 hit it's end-of-life (April 30, 2013) just a month after this bug was filed 
(March 29, 2013) and the 2.7 EOL was just announced for October 2013. Even if 
this can be reproduced, the 2.x series is dead and this is probably a WONTFIX.

----------------------------------------
Bug #19994: Puppet attempts to write authorized keys to the wrong user
https://projects.puppetlabs.com/issues/19994#change-94527

* Author: Nick Chappell
* Status: Closed
* Priority: Normal
* Assignee: Roger Kennedy
* Category: ssh
* Target version: 
* Affected Puppet version: 2.6.17
* Keywords: customer
* Branch: 
----------------------------------------
Puppet is attempting to write SSH authorized keys to the wrong users' 
~/.ssh/authorized_keys file.

This is different than http://projects.puppetlabs.com/issues/13973 as the 
temporary file is successfully created during the run. However, because Puppet 
writes an authorized key with the permissions of the user the key is for (due 
to https://puppetlabs.com/security/cve/cve-2011-3870/ ), writing to another 
user's authorized_keys causes the Puppet run to fail.




-- 
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://projects.puppetlabs.com/my/account

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to