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

adds S/NTRUP1277 #1111

Merged
merged 3 commits into from
Oct 22, 2021
Merged

adds S/NTRUP1277 #1111

merged 3 commits into from
Oct 22, 2021

Conversation

baentsch
Copy link
Member

@baentsch baentsch commented Oct 18, 2021

Fixes #1108

  • Does this PR change the input/output behaviour of a cryptographic algorithm (i.e., does it change known answer test values)? (If so, a version bump will be required from x.y.z to x.(y+1).0.)
  • Does this PR change the the list of algorithms available -- either adding, removing, or renaming? (If so, PRs in OQS-OpenSSL, OQS-BoringSSL, and OQS-OpenSSH will also be required by the time this is merged.)

Add/Edit:

@baentsch
Copy link
Member Author

Would someone with a Mac have time to look into the apparently Apple-specific length limitation failing CI? In the worst case, I will disable some algorithms from the default build on OSX to get this to pass on that platform. (Other) Proposals welcome. Thanks in advance.

@dstebila
Copy link
Member

I'm unable to reproduce on my system; I even tried downgrading to the exact version of CMake used on CircleCI but that didn't make it happen.

I tried some of the ideas I found by Googling: 1, 2, in particular adding the following lines to CMakeList.txt:

# avoid too-long command lines
# https://stackoverflow.com/questions/43184251/cmake-command-line-too-long-windows
set(CMAKE_C_USE_RESPONSE_FILE_FOR_OBJECTS 1)
set(CMAKE_C_RESPONSE_FILE_LINK_FLAG "@")
set(CMAKE_NINJA_FORCE_RESPONSE_FILE 1 CACHE INTERNAL "")

but then I got a build failure. Link 2 above actually comments that it's tricky to make this work reliably. I'm not sure what to suggest.

@baentsch
Copy link
Member Author

baentsch commented Oct 19, 2021

I'm unable to reproduce on my system [...] I'm not sure what to suggest.

Thanks for running it on your system. If it's working there this is a CircleCI issue and putting work on fixing that isn't really worth the effort. What about simply disabling a family for shared OSX CCI runs? What about McEliece? Would also speed up CI considerably. WillDid put a note into the platform-specific build Wiki .

@dstebila
Copy link
Member

Thanks for running it on your system. If it's working there this is a CircleCI issue and putting work on fixing that isn't really worth the effort.

Hard to tell where the problem is at this point, so:

What about simply disabling a family for shared OSX CCI runs? What about McEliece? Would also speed up CI considerably.

Yeah I guess that would be fine for now.

@baentsch baentsch marked this pull request as ready for review October 20, 2021 05:46
@baentsch baentsch requested a review from dstebila October 22, 2021 06:44
@dstebila dstebila merged commit 6175da8 into main Oct 22, 2021
@dstebila dstebila deleted the mb-ntru1277 branch October 22, 2021 13:31
@dstebila
Copy link
Member

Thanks Michael!

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

Successfully merging this pull request may close these issues.

Add NTRU Prime NIST Level 5 parameter set sntrup1277 and ntrulpr1277
2 participants