[JIRA] Commented: (SSPCPP-503) shibd binary uses wrong libcurl on RHEL6

[Scott Cantor (JIRA)]

    [ https://issues.shibboleth.net/jira/browse/SSPCPP-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14403#comment-14403 ] 

Scott Cantor commented on SSPCPP-503:
-------------------------------------

Or are you referring to my suggestion that we fix the log message? That was all I was thinking of doing. Not really because of the command line per se, that threw me off. ;-)

> shibd binary uses wrong libcurl on RHEL6
> ----------------------------------------
>
>                 Key: SSPCPP-503
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-503
>             Project: Shibboleth SP - C++
>          Issue Type: Bug
>      Security Level: Standard(Standard bug, may impact functionality but does not represent a security vulnerability ) 
>    Affects Versions: 2.5.0
>         Environment: RHEL 6.3
>            Reporter: martin.haase at idp.protectnetwork.org
>            Assignee: Scott Cantor
>            Priority: Minor
>
> When invoking the shibd executable directly (instead of using the init script), on RHEL6 the wrong libcurl is linked. This leads, among other things, to a warning when trying to download metadata over https.
> One instance of this bug:
> # shibd -t 
> 2012-09-21 12:17:11 ERROR XMLTooling.libcurl.InputStream : error while fetching https://metadata-server/metadata.xml: (59) Unknown cipher in list: ALL:!aNULL:!LOW:!EXPORT:!SSLv2
> 2012-09-21 12:17:11 ERROR XMLTooling.ParserPool : fatal error on line 0, column 0, message: internal error in NetAccessor
> 2012-09-21 12:17:11 ERROR OpenSAML.MetadataProvider.XML : error while loading resource (https://metadata-server/metadata.xml): XML error(s) during parsing, check log for specifics
> 2012-09-21 12:17:11 WARN OpenSAML.MetadataProvider.XML : adjusted reload interval to 600 seconds
> 2012-09-21 12:17:11 WARN OpenSAML.MetadataProvider.XML : trying backup file, exception loading remote resource: XML error(s) during parsing, check log for specifics
> overall configuration is loadable, check console for non-fatal problems

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira