Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find a solution to avoid the need to recompile openssl #30

Open
rhertzog opened this issue May 16, 2014 · 2 comments
Open

Find a solution to avoid the need to recompile openssl #30

rhertzog opened this issue May 16, 2014 · 2 comments

Comments

@rhertzog
Copy link

As you have noticed ssl3_write_bytes() is internal to openssl and is thus not exported in openssl iibrary provided by Debian and Kali Linux. Your workaround works well but doesn't allow for proper packaging. Linking with static libraries is frowned upon in the Debian policy and downloading openssl during the build of heartleech is also forbidden (but I did that for Kali Linux anyway)...

Would it be possible to duplicace just ssl3_write_bytes in the heartleech source code and otherwise dynamically link with OpenSSL ?

Thanks for considering.

@robertdavidgraham
Copy link
Owner

Firstly, this policy regarding OpenSSL is wrong. It should never be linked as a dynamic-library because it doesn't have an ABI. That's why the entire library has been deprecated under Mac OS X, as explained in this link:
http://www.metzdowd.com/pipermail/cryptography/2014-April/020977.html

Yes, I hate this dependency. I looked into what it would take to directly include the code and found this would require further internal functions and knowledge of internal structures. I can probably reduce the amount I'd need to important because there's lots of optional code that's skipped over, not needed for my specific calls, but I'd have to step through with a debugger to be sure.

@robertdavidgraham
Copy link
Owner

By the way, thank you for your help on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants