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.

Sign up for GitHub

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

Jump to bottom

Use various providers in JCA #32

Open
3 tasks
hugoqnc opened this issue Jul 2, 2024 · 0 comments
Open
3 tasks

Use various providers in JCA #32

hugoqnc opened this issue Jul 2, 2024 · 0 comments
Labels
enhancement New feature or request java plugin issues related to the java implementation

Comments

@hugoqnc
Copy link
Contributor

hugoqnc commented Jul 2, 2024

JCA uses a provider-based architecture, where one can specify a cryptography provider (like BouncyCastle) which will provide the implementations of JCA APIs.

  • Investigate if we can often identify the provider when tracking JCA crypto calls
  • If so, restructure the JCA rules to make them depend on the provider
  • Add BouncyCastle as a cryptography provider for JCA
@hugoqnc hugoqnc added enhancement New feature or request java plugin issues related to the java implementation labels Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request java plugin issues related to the java implementation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hugoqnc