-
Notifications
You must be signed in to change notification settings - Fork 218
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 running CCF on Azure Linux #6588
Comments
@maxtropets current is 3.3.2, so that one :) |
Currently removed the Checked OpenSSL source, same NID for 3.1 and 3.3 impl, NID matches.
Needs investigation. |
Tried all other unit tests (crypto test patched with #6591)
|
256k1 is not a NIST standard, which is likely why SymCrypt rejects it - it would be good to confirm and document though |
Figured out it's not explicitly linked, but rather being loaded during runtime
Confirmed dependency chain ccf -> librypto -> libsymcrypt (monolithic lib):
|
Split into smaller sub-issues except UPD: Fixed in #6598 |
Got to the bottom of UVM endorsements test failure, filed a ticket (#6600) So far, all the known issues are filed in sub-issues or solved. Next steps
|
Dumping to not lose, how to run the container + tests
|
In this issue have to support building and testing CCF on Azure Linux.
The major obstacle so far - openssl.
On Azure Linux, we shall use OpenSSL of (major) version 3. It is to be determined in this ticket which exact version is supported by Azure Linux.
Ticket for reference: #5291
Subtasks to track the progress
./crypto_test
(patched, see discussions in comments)The text was updated successfully, but these errors were encountered: