gosop inline-sign fails with "Unsupported option"

[dkg]

I'm running this test on debian testing:

0 dkg@alice:~$ gosop inline-sign
Please provide keys to create detached signature
69 dkg@alice:~$ gosop version --extended
gosop 0.1.0
GopenPGP 2.5.2
Compiled using go1.20.5
0 dkg@alice:~$ echo test | gosop inline-sign tester.key
Unsupported option
37 dkg@alice:~$ 

[dkg]

gosop inline-sign appears to work if i pass it --as=clearsigned though.

[lubux]

Hi DKG. Thanks for the issue. The gosop implementation on the main branch currently does not support inline signatures (except clearsigned). Nevertheless, an updated version 3 of GopenPGP is currently in development and the gosop-gopenpgp-v3 branch in this repo implements gosop with the new version. It implements most of the latest api in draft-dkg-openpgp-stateless-cli-06 and implements all the crypto-refresh features as well. Feel free to try this version ;)

[dkg]

@lubux thanks for this! I've encouraged the openpgp interop test suite to include gosop-v3. You might want to comment over there if there's a specific tag or branch label that you'd like the interop test suite to pull from.

[lubux]

Great. Pulling from the gosop-gopenpgp-v3 branch as it is done now is fine as long as it is still marked as not stable.

[dkg]

it's been over a year since we had the conversation above. any chance that we can get a release of the v3 branch?

[twiss]

@lubux Is on vacation for the coming two weeks, and I will be soon too. Most likely we'll make a release after that (in mid August), especially when the stable version of gopenpgp v3 is released :blush:

[mdosch]

@dkg I just uploaded an build of gosop that uses gopenpgp v3 alpha to experimental:

gosop version --extended
gosop 2.0.0-alpha
GopenPGP 3.0.0-alpha.3
Compiled using go1.22.6

Although it identifies as GopenPGP 3.0.0-alpha.3, it's built using GopenPGP 3.0.0-alpha.4. Seems the version was not updated when releasing the latest alpha.

[dkg]

thanks! it's exciting to see this progress

[dkg]

a gentle nudge here -- it'd be great to move the release along. we're a bit past "mid August" 😉

[twiss]

I've tagged release v1.0.0 :)