> Do you have examples of what the new output looks like with this change?
Here's some example output: $ pkg image-create -F -a sidewinder=https://sidewinder.red.iplanet.com/dev/promoted/solaris-sparc $PKG_IMAGE pkg: 0/1 catalogs successfully updated: Could not retrieve catalog from 'sidewinder' URLError, reason: (1, 'error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol') > While this eliminates the traceback, it doesn't provide any clue to the > user as to what to do next, especially if this is a case where the > problem is that the user has not provided a cert/key and one is > required. That was the intent when the issue was filed. It's most important that we solve the issue with the traceback first. I realize you don't like the format of the error messages we're getting; however, you don't seem to be listening to my explanation of why they are the way that they are. pyOpenSSL has wretched error handling. Anytime the library encounters an OpenSSL error, it creates a sslerror exception, calls the OpenSSL equivalent of strerror() and sticks the string in the exception. As a programmer, I have no way of determing what went wrong simply by looking at the exception that occured. It's beyond the current sophistication of the pkg client to parse "error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol" and determine that I'm using a busted proxy configuration. I don't want to spend a lot of time polishing this turd, especially since we're going to swap out the underlying transport mechansim post-2008.11. It's my hope that the new transport will make it a lot easier for us to get SSL working properly. -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
