[bug-notifications] [openssl 0004931]: "git clone https: ..." fails: Request to upgrade OpenSSL to 1.0.0h or newer.
Mantis Bug Tracker
noreply at opencsw.org
Sun Apr 29 19:41:00 CEST 2012
The following issue requires your FEEDBACK.
======================================================================
https://www.opencsw.org/mantis/view.php?id=4931
======================================================================
Reported By: zephyrus00jp
Assigned To: yann
======================================================================
Project: openssl
Issue ID: 4931
Category: upgrade
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
======================================================================
Date Submitted: 2012-04-02 15:50 CEST
Last Modified: 2012-04-29 19:41 CEST
======================================================================
Summary: "git clone https: ..." fails: Request to upgrade
OpenSSL to 1.0.0h or newer.
Description:
On solaris 10, I found that
git clone https:....
failed.
To make a long story short, I tracked down this to the failure of curl
library used by git, and then this curl library seems to be failing
in openssl modules.
The following is more detailed explanation and my fiding:
serverfault.com/questions/374053/solaris-10-opencsw-git-package-issue-with-bitbucket-git-hosting
Based on some similar reports, I think it is best to
offer openssl 1.0.0h or newer, and then re-compile curl libraries (making
sure that openssl versions are used), and recompile git tools as well.
I don't know much about OpenCSW packaging and so I can't try to
recompile openssl and figure out whether upgrading helps or not.
======================================================================
----------------------------------------------------------------------
(0009844) yann (manager) - 2012-04-29 19:41
https://www.opencsw.org/mantis/view.php?id=4931#c9844
----------------------------------------------------------------------
Hi,
Is your problem still current ?
If it's the case, could you run the command that failed with truss:
truss -o /tmp/truss.out -f command
and attach the truss output (truss.out) to this bug ?
Yann
More information about the bug-notifications
mailing list