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

Quarkus requires the public key to be present at build time, preventing it from using keys generated at runtime #23590

Closed
rafaelfnx opened this issue Feb 10, 2022 · 3 comments
Labels
area/security kind/bug Something isn't working
Milestone

Comments

@rafaelfnx
Copy link

Describe the bug

I had already created an issue, but even after about a month and a half it got no response, the only thing I got was a comment with a proposal from @sberyozkin, but he hasn't responded in the last 44 days, so since the last issue is dead, I'm creating a new one to try to come up with a solution to the problem. The original issue is #22536.

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

@sberyozkin
Copy link
Member

sberyozkin commented Feb 10, 2022

@rafaelfnx Hi, I've closed the original issue as a duplicate.

Note, there are many issues each of us has to deal with, unfortunately we can't prioritize immediately on every new issue reported.
But also, please appreciate it is an open source project - so you are welcome to help and open a PR if it is an urgent issue for you
Thanks

@sberyozkin
Copy link
Member

@rafaelfnx By the way, looks like @radcortez has fixed it: #23421

@geoand
Copy link
Contributor

geoand commented Feb 11, 2022

Note, there are many issues each of us has to deal with, unfortunately we can't prioritize immediately on every new issue reported.

Very much +1

@rafaelfnx please try version 2.7.1.Final and see if it fixes your issue. In the meantime I am going to close this as #23421 seems to address this exact issue. If not, feel free to comment.

@geoand geoand closed this as completed Feb 11, 2022
@geoand geoand added this to the 2.7.1.Final milestone Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/security kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants