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

Review project status #108

Closed
baentsch opened this issue Jan 24, 2024 · 3 comments
Closed

Review project status #108

baentsch opened this issue Jan 24, 2024 · 3 comments

Comments

@baentsch
Copy link
Member

In checking all OQS subproject statuses we've also come across this project: It doesn't seem overly active (e.g., actively following the upstream master), so we wonder whether this should somehow be reflected in the README. @pi-314159 any suggestions in this regard?

@pi-314159
Copy link
Member

I agree. Here is the current plan

  • Update boringssl every 2-3 months; I’ll bring X25519 hybrid algorithms to boringssl in the next update
  • Build a new Chromium when liboqs has a new release

@baentsch
Copy link
Member Author

Build a new Chromium when liboqs has a new release

There's been a liboqs release, so where do we put a new Chromium build (and for which platforms)?

@pi-314159
Copy link
Member

Yes I noticed that. We're on the spring festival holiday now; we will build one in early March.

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