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
Support OpenSSL v1.1.0b in v3.0.x #1817
Comments
I suppose.
You're free to submit a patch. |
|
It's fully supported in v3.1.x and v4.0.x so you should be able to pull in the fixes from there. |
|
Thanks, @alandekok, I know, I'm always free to submit patches :) The question was rather if you're going to do it in the near future. I'll see if I can find the time to do it myself. @arr2036 Thanks, I'll look for them. Can you tell what I should be looking for in the history to pinpoint the commits necessary? Or perhaps, what were the major changes adding support, in general? |
|
The point is that this is open source. No one gets paid to work on it. Filing a bug and asking "when will this be fixed?" comes across as demanding that we jump immediately to make you happy. Which isn't friendly. The file "mppe_keys.c" is in the same location in v3.1.x and in v3.0.x. Perhaps looking there would be a good idea. |
|
@alandekok Sorry, didn't mean to come across that way, tried to be polite. Will work on my wording. Sure, I looked at the differences, couldn't see what exactly is changing and assumed it wouldn't be the only place broken. So, not being able to fix it quickly myself came here with the question and a hope. Will look again. |
|
For the record, the same issue happens on v3.1.x: |
|
Yeah apparently they added more things after the first alpha releases sigh. @alandekok is looking at fixing it in v4.0.x. |
|
Just an update: I finally got it to build, but with a bunch of warnings. Will hunt them down and submit a draft pull request this week. |
|
Thanks a lot, @herwinw, I will! |
|
Is this issue resolved now? |
|
Yes, it is, thank you. |
Issue type
Defect/Feature description
The v3.0.12 release, as well as the latest FreeRADIUS v3.0.x branch don't
build with OpenSSL v1.1.0b, in particular in Fedora Rawhide with openssl
package version 1:1.1.0b-3.fc26:
Would it be possible to make FreeRADIUS v3.0.x build with OpenSSL v1.1.0b?
If yes, then when, and when a release supporting it will be available?
Thank you.
The text was updated successfully, but these errors were encountered: