Skip to content

Make `sop armor` idempotent by default

I can't think of a reasonable use case for nested ascii armor. If sop armor is called on already armored text, nesting that into a "message" type armor is very likely not what the user intended. With this modification sop armor becomes useful as a "make sure this is armored" pipe operation.

Another option here would be to error by default.

Merge request reports

Loading