Hi kbannister,
Quote Originally Posted by kbannister View Post
How do you know all this stuff!! Will I ever learn it!
well, I read a lot... man pages, documentation, web pages

Quote Originally Posted by kbannister View Post
I renamed the x86_64 directory to x86_64.org. Ran zypper up and the patches installed. Yay. I can't reboot for another hour so hope it all worked.
Please take the output from "rpm -Va" serious (if still persisting after that recent update), as other programs may be damaged, too - a probable cause is some file system or disk problem, so running "fsck -f" on that file system isn't really optional now.


Quote Originally Posted by kbannister View Post
I did get this error at the end. Do you know what that means.
Yes. If you're actually running puppet (rather than just having the software installed), you need to fix your configuration.

Quote Originally Posted by kbannister View Post
Please refer to the documentation in
/usr/share/doc/packages/puppet/puppetlabs-cve20113872-0.0.5
for detailed instructions and scripts.

Puppetlabs' site also provides more information:
http://puppetlabs.com/security/cve/cve-2011-3872/faq/
http://puppetlabs.com/blog/important...vulnerability/
The local documentation and the FAQ tell you what this is about.

If you don't actually run puppet, then remove it (or fix the config anyhow) - a later user may expect this to be fixed already and will not receive another notice, this would impose e security risk.

Regards,
Jens