-
Notifications
You must be signed in to change notification settings - Fork 55
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
require Botan 2.14.0 #1371
require Botan 2.14.0 #1371
Conversation
7ab1171
to
f1eb059
Compare
@ronaldtse Looks like we need to put correct version of botan to https://github.com/riboseinc/yum |
f1eb059
to
dbb1be6
Compare
@dewyatt could you help with it since you are familiar? Thanks! |
dbb1be6
to
fbdfb07
Compare
@ronaldtse It's been a while and it looks like there are some issues here. I think I would need maintainer access on GitLab ribose/rpm-spec-botan2 to troubleshoot this. |
@ribose-jeffreylau could you help here? It would probably be better to move this yum repository to GitHub... |
@dewyatt I gave you maintainer access to https://gitlab.com/ribose/rpm-spec-botan2. Since we don't have a subscription at GitLab, we can no longer mirror GitHub repos in GitLab, that's why the updates aren't automatically built. I manually pushed your changes to GitLab to see if it built --- there're some errors that may require your help. @ronaldtse Should we investigate moving all the rpm-spec-* CI from GitLab to GitHub? |
@ribose-jeffreylau we should definitely move all the repos (and workflows) from GitLab back to GitHub, especially since GitHub now supports this type of workflow. |
Well that's unfortunate they took mirroring out of the free tier. |
I think I remember when I migrated these to GitLab that GHA didn't (at the time) have a feature like include:remote (used here), so that may be one of the challenges in migrating those back. But GHA has improved a lot since then, so... |
fbdfb07
to
20a7382
Compare
I think this PR would need an update here as well: Line 19 in 57c8afb
(We build most direct dependencies manually in centos CI to get useful stacktraces with ASaN, the RPM is more for end-users) |
20a7382
to
5f959f5
Compare
@dewyatt Since there is version 2.16 of Botan in MSYS2 and VCPKG repositories for WIndows, maybe we should use 2.16 everywhere? |
Sounds reasonable to me! |
5f959f5
to
1a935a8
Compare
@ni4 Can you please advise on how to add additional setup steps for CIFuzz? To be exact, how to install Botan manually as we do in other steps, because there is Botan 2.12.1 out of the Ubuntu box. |
We'll probably have to do some updates to oss-fuzz for this |
Yeah, that's right - Botan for oss-fuzz is installed here: https://github.com/google/oss-fuzz/blob/51098cb7917a822bd8f3adc047c20126c5283113/projects/rnp/build.sh#L20 I'll do a PR and write back once it is merged. |
Tracked via google/oss-fuzz#4900 |
For CMake you mean? I would say we should keep that at the minimum that builds and passes tests for most platforms, which is probably 2.8.0 (some FFI support for x25519 was added there). 2.9.0 might be better since that fixes CVE-2018-20187 (seems relevant to us). |
@dewyatt Didn't we need to update to 2.14.0 because of As an alternative we may introduce some variable like CMAKE_FORCE_BOTAN_VERSION, allowing to build with older then 2.14 |
I haven't been keeping up with RNP like I used to so you guys are probably in a better place to make that call, but I don't believe this one affects us.
I can also say that adding |
Happy New Year, guys! @dewyatt Actually, I think it's more 'political' - to not allow others, who don't dig that deep as you, say 'rnp uses Botan with vulnerabilities'. So I'd vote for 2.14 at least. |
ca2248f
to
24472d9
Compare
9d3591f
to
5f1338c
Compare
5f1338c
to
25b881a
Compare
@rrrooommmaaa Looks like Windows/MSYS2 workflow still hangs due to Botan's update. |
Yes. And setting |
Feel free to continue on this. I spent a lot of time on this year ago, and wasn't able to find a solution, unfortunately. |
So is it because of |
I don't know, If I know I'd resolve it :) Shared libraries are required for the ruby-rnp, but those tests are not run for msys2/mingw. It would be good to investigate and find the real reason for this problem, to be aware of it in the future. |
I understand. But how much time is reasonable to spend on this, @ronaldtse ? |
I can take a look today, it's not that hard to work around it. EDIT: I did test a couple of workarounds successfully, I'll try to get something out today but I'm slightly out of commission with back pain at the moment. |
I filed randombit/botan#2582 and and created msys2/MINGW-packages#7640. I'll try to get an immediate workaround in here now. |
Good! Thanks for your effort in this complicated matter. |
When the test succeeds, we'll need to restore CTEST_PARALLEL and probably timeout settings too. |
Seems that the Windows test ran out of time at 3 hours at test 205:
Stuck? |
Yeah, looks like updated Botan package didn't get into distribution yet. |
ci/before_install.sh
Outdated
@@ -91,8 +91,8 @@ msys_install() { | |||
mingw64/mingw-w64-x86_64-python3 | |||
" | |||
pacman --noconfirm -S --needed ${packages} | |||
botan_pkg="mingw-w64-x86_64-libbotan-2.13.0-1-any.pkg.tar.xz" | |||
pacman --noconfirm -U http://repo.msys2.org/mingw/x86_64/${botan_pkg} || \ | |||
botan_pkg="mingw-w64-x86_64-libbotan-2.16.0-1-any.pkg.tar.zst" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rrrooommmaaa Could you please update it here to mingw-w64-x86_64-libbotan-2.17.3-2-any.pkg.tar.zst
as only since this version MinGW applies Daniel's patch from https://github.com/msys2/MINGW-packages/pull/7640/files? I can do it myself, but then we'll end up with rebase/merge hell due to force-push.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P.S. And add some comment why that specific version is used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah sorry I dropped the ball on this but I have to step away for a few days. That is hopefully a quick solution, I was going to just do a makepkg w/thread_utils disabled in CI so we could have 2.16 across the board, but really I don't think it's that important and your solution should be quicker and easier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rrrooommmaaa Could you please update it here to
mingw-w64-x86_64-libbotan-2.17.3-2-any.pkg.tar.zst
as only since this version MinGW applies Daniel's patch from https://github.com/msys2/MINGW-packages/pull/7640/files? I can do it myself, but then we'll end up with rebase/merge hell due to force-push.
Sure.
@rrrooommmaaa Finally all green! Let's squash it to the single commit and approve. |
Thank you guys!! |
Closes #1279