Add test plan for QUARKUS-3456

[michalvavrik]

Links

JIRA: https://issues.redhat.com/browse/QUARKUS-3456

Quarkus documentation: https://quarkus.io/version/main/guides/config-secrets#protect-the-keystore-password

Reminder for considerable topics

• Make sure you have considered the following areas when preparing the test plan:

  • Logging
  • Tracing
  • Metrics
  • Security
  • OpenAPI
  • Data sources
  • Frontend
  • Qute

[rsvoboda]

Few things to handle + we need confirmation of scope from https://issues.redhat.com/browse/QUARKUS-3456?focusedId=25160816&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-25160816

[rsvoboda]

I would prefer to move it out of the future scope and put it into current TD.
What would be the estimate to implement this?

[michalvavrik]

You can chose alg/mode/padding via CLI encrypt cmd options https://github.com/quarkusio/quarkus/blob/main/devtools/cli/src/main/java/io/quarkus/cli/config/Encrypt.java#L59 but I am worried about this https://github.com/quarkusio/quarkus/blob/main/devtools/cli/src/main/java/io/quarkus/cli/config/Encrypt.java#L64. I simply didn't get to test this and I don't know if you can use different cipher while you still have there GCM spec 128 and sha256.

I cannot tell if it is additional time or not, but quarkusio/quarkus#34493 said Can encrypt arbitrary values in AES/GCM/NoPadding (will support more algorithms) so I didn't expect it is actually supported. Right now, it is not documented which other ciphers are supported.

[michalvavrik]

@rsvoboda

    @Option(hidden = true, names = { "-a", "--algorithm" }, description = "Algorithm", defaultValue = "AES")
    String algorithm;

    @Option(hidden = true, names = { "-m", "--mode" }, description = "Mode", defaultValue = "GCM")
    String mode;

    @Option(hidden = true, names = { "-p", "--padding" }, description = "Padding", defaultValue = "NoPadding")
    String padding;

    @Option(hidden = true, names = { "-q", "--quiet" }, defaultValue = "false")
    boolean quiet;

they are hidden, that and the fact it is not documented says it all, it is not supported ATM IMHO

[michalvavrik]

https://issues.redhat.com/browse/QUARKUS-3456?focusedId=25161121&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-25161121

[michalvavrik]

we need confirmation of scope from

in a case scope wouldn't be confirmed, this would be blocked till TD is merged, I prefer to update TP later

[rsvoboda]

confirmation of scope / update of TP/TD can come later in separate PRs

[rsvoboda]

LGTM, thanks for quick update. Open questions can be reflected once we get feedback on them.