Correct checks for redirected I/O during interactive token resealing

1 files changed, 1 insertions, 1 deletions

diff --git a/vespaclient-java/src/main/java/com/yahoo/vespa/security/tool/crypto/DecryptTool.java b/vespaclient-java/src/main/java/com/yahoo/vespa/security/tool/crypto/DecryptTool.java
index 4b3608fc3f7..8c85f7be49d 100644
--- a/vespaclient-java/src/main/java/com/yahoo/vespa/security/tool/crypto/DecryptTool.java
+++ b/vespaclient-java/src/main/java/com/yahoo/vespa/security/tool/crypto/DecryptTool.java
@@ -146,7 +146,7 @@ public class DecryptTool implements Tool {
 
     private static SecretSharedKey secretFromInteractiveResealing(ToolInvocation invocation, String inputArg,
                                                                   String outputArg, SealedSharedKey sealedSharedKey) throws IOException {
-        if (!CliUtils.useStdIo(outputArg) || !CliUtils.useStdIo(inputArg)) {
+        if (CliUtils.useStdIo(outputArg) || CliUtils.useStdIo(inputArg)) {
             throw new IllegalArgumentException("Interactive token resealing not available with redirected I/O");
         }
         var session = SharedKeyResealingSession.newEphemeralSession();