Issue #8969 has been updated by Daniel Pittman. Description updated
Franz Pletz wrote: > Can this be solved by treating FIFOs and for instance Sockets specially? As > it makes no sense for puppet to manage the contents of such special files, > opening and reading/writing should not take place in the first time. Patch > should be easy and I would do it if this fix suffices. Absolutely. We don't actually support creating them, or block and character special devices, in Puppet, so we only have to watch for, eg, people telling us to manage them. ---------------------------------------- Bug #8969: Puppet hangs trying to replace a FIFO https://projects.puppetlabs.com/issues/8969 Author: Daniel Pittman Status: Accepted Priority: High Assignee: Category: file Target version: 2.7.x Affected Puppet version: 2.6.0 Keywords: Branch: Puppet does some stupid things trying to replace a FIFO, including opening it and trying to MD5 the content. This allows a DoS for any managed file that can be replaced with a disconnected FIFO, at least. To reproduce: <pre> mkfifo /tmp/boom puppet apply <<EOT file { "/tmp/boom": ensure => file, content => "Hello, World" } EOT </pre> -- 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 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.
