Jira (PUP-3522) Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module

[Josh Cooper (JIRA)]

Title: Message Title

Josh Cooper commented on an issue   Re: Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module Ideally all networking connections would go through Puppet::Network::HTTP.http_instance so that we can ensure we disable insecure protocols, e.g. SSLv2/3, allow the ciphersuite string to be specified, etc. However, some code paths don't, notably anything using open-uri. As a result, we monkey patch to ensure that doesn't happen. Long term, we should remove usage of open-uri, e.g. PMT, appdmg & pkgdmg providers, etc, and then move the monkey patch to our http connection factory. Short term, we might be able to skip the monkey patch when running in JRuby? Add Comment   Puppet / PUP-3522 Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module When [~andrew.roetker] first tried to bring up JVM-Puppet on Debian, he encountered an "OpenSSL::X509::StoreError" -- stack trace below. This happened during initialization of one of the JRuby ScriptingContainers for Ruby Puppet use during launch of the Java process. We have yet to be able to reproduce anything like this when running JVM-Puppet on CentO... 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.