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

The fix for opensslconf.h path shouldn't be restricted to Ubuntu 13.04 #1

Open
vcarel opened this issue Oct 14, 2015 · 5 comments
Open

Comments

@vcarel
Copy link

vcarel commented Oct 14, 2015

I think the fix for opensslconf.h path (/usr/include/x86_64-linux-gnu/openssl/) should be applied to all debian distribs (at least >= Jessy).

In my case, i'm developping under Ubuntu 15.04 and packaging my app with Docker Python 2.7, so on Debian Jessy. In both distribs the opensslconf.h file is at the same location.

BTW, do you know what's the situation with M2Crypto ? Is it maintained or what ?

@vcarel vcarel changed the title The fix for opensslconf.h on ubutun shouldn't be restricted to Ubuntu 13.04 The fix for opensslconf.h path shouldn't be restricted to Ubuntu 13.04 Oct 14, 2015
@allardhoeve
Copy link

Ran into this today as well. It seems M2Crypto is unmaintained. Someone picked up the pieces though and moved to gitlab: https://gitlab.com/m2crypto/m2crypto/

@vcarel
Copy link
Author

vcarel commented Oct 14, 2015

Anyway, congrats for the SSLv2 patch & fork & stackoverflow anwser. You saved my day :-)

@allardhoeve
Copy link

Not a problem :)

On Wed, Oct 14, 2015 at 3:03 PM Vianney Carel notifications@github.com
wrote:

Anyway, congrats for the SSLv2 patch & fork & stackoverflow anwser
http://stackoverflow.com/a/14835020/1202385. You saved my day :-)


Reply to this email directly or view it on GitHub
#1 (comment).

@allardhoeve
Copy link

@vcarel
Copy link
Author

vcarel commented Oct 14, 2015

Nice. Thanks.

2015-10-14 16:02 GMT+02:00 Allard Hoeve notifications@github.com:

https://gitlab.com/m2crypto/m2crypto/merge_requests/5


Reply to this email directly or view it on GitHub
#1 (comment).

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