Bug 13858 - libssl.so.0.9.8 is missing and prevents Evasi0n jailbreak software to show a gui.
Summary: libssl.so.0.9.8 is missing and prevents Evasi0n jailbreak software to show a ...
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: Backports (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-04 19:29 CEST by Kristoffer Grundström
Modified: 2014-08-04 19:34 CEST (History)
2 users (show)

See Also:
Source RPM: libssl
CVE:
Status comment:


Attachments

Description Kristoffer Grundström 2014-08-04 19:29:11 CEST
Description of problem: The jailbreak software for various IOS versions needs libssl.so.0.9.8 to open the gui in Mageia.

The error I see when running the binary is this:

./evasi0n.x86: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory

I used urpmf libssl.so.0.9.8 to see if it exists in Mageia 4 but found no result.

I then used rpm.pbone.net to look for the same file, but it existed in another package on another dist.

Version-Release number of selected component (if applicable): 0.9.8

How reproducible: All the time.

Steps to Reproduce:
1. Open the webbrowser of choice. 
2. Open the adress http://jbmodo.com/1a9Yl1z
3. Download the archive,
4. Unpack it.
5. Install libgtk+2.0-devel and libopenssl-devel (since libssl-devel no longer exists)
6. Run the binary that fits your CPU.
7. Voila! You should get the same message.

Reproducible: 

Steps to Reproduce:
Kristoffer Grundström 2014-08-04 19:29:52 CEST

CC: (none) => kristoffer.grundstrom1983

Comment 1 Sander Lepik 2014-08-04 19:34:32 CEST
Our openSSL version is 1.0.0. We won't downgrade it.

You can try this command: ln -s /usr/lib/libssl.so.1.0.0 /usr/lib/libssl.so.0.9.8 - it might work but there is no guarantee.

Status: NEW => RESOLVED
CC: (none) => mageia
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.