From 6ec62560ba3474662239f24c1bb7a8c3e6081d2b Mon Sep 17 00:00:00 2001 From: Paul Schaub Date: Mon, 17 Apr 2023 13:13:36 +0200 Subject: [PATCH] Add comment about why --as=clearsigned and --no-armor are incompatible --- .../src/main/java/sop/cli/picocli/commands/InlineSignCmd.java | 1 + 1 file changed, 1 insertion(+) diff --git a/sop-java-picocli/src/main/java/sop/cli/picocli/commands/InlineSignCmd.java b/sop-java-picocli/src/main/java/sop/cli/picocli/commands/InlineSignCmd.java index 7e7c8af..773e6af 100644 --- a/sop-java-picocli/src/main/java/sop/cli/picocli/commands/InlineSignCmd.java +++ b/sop-java-picocli/src/main/java/sop/cli/picocli/commands/InlineSignCmd.java @@ -41,6 +41,7 @@ public class InlineSignCmd extends AbstractSopCmd { InlineSign inlineSign = throwIfUnsupportedSubcommand( SopCLI.getSop().inlineSign(), "inline-sign"); + // Clearsigned messages are inherently armored, so --no-armor makes no sense. if (!armor && type == InlineSignAs.clearsigned) { String errorMsg = getMsg("sop.error.usage.incompatible_options.clearsigned_no_armor"); throw new SOPGPException.IncompatibleOptions(errorMsg);