On Mon, Aug 04, 2014 at 09:43:29AM -0400, Michael K. Johnson wrote: > Yes, as you imply, this does leave the potential for a MITM attack > to compromise the client entitlement information. This was due > to a long-standing lack of certificate enforcement in Python's > SSL support. Fixing that was never highest priority for any rPath > customers, though a few were mildly concerned. To the best of > my knowledge...
Aha! I am wrong! https://opensource.sas.com/its/browse/CNY-2735 https://opensource.sas.com/its/browse/CNY-2301 It appears that I was the one who released the version of Conary that remedied this bug, but had no recollection of the fact, and the issue I found in the issue tracking system wasn't the issue that was referenced when the issue was resolved; it was not then linked as a duplicate. So you can point trustedCerts at certificate bundles by naming directories and/or globs to identify the trusted certs. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
