[BUG] Signed messages can't be verified by keyoxide #205

3v1n0 commented 2024年11月04日 23:09:35 +01:00

What happened

Use profile signature (https://keyoxide.org/sig), using your own text or the example one from documentation:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hey there! Here's a signature profile with proofs related to the DOIP project (https://doip.rocks).
Verify this profile at https://keyoxide.org/sig
proof=dns:doip.rocks
proof=https://fosstodon.org/@keyoxide
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEENjcgJSPnwTCat56Z7y3FgntEX0sFAl/7L0MQHHRlc3RAZG9p
cC5yb2NrcwAKCRDvLcWCe0RfS3iYC/0QQqz2lzSNrkApdIN9OJFfd/sP2qeGr/uH
98YHa+ucwBxer6yrAaTYYuBJg1uyzdxQhqF2jWno7FwN4crnj15AN5XGemjpmqat
py9wG6vCVjC81q/BWMIMZ7RJ/m8F8Kz556xHiU8KbqLNDqFVcT35/PhJsw71XVCI
N3HgrgD7CY/vIsZ3WIH7mne3q9O7X4TJQtFoZZ/l9lKj7qk3LrSFnL6q+JxUr2Im
xfYZKaSz6lmLf+vfPc59JuQtV1z0HSNDQkpKEjmLeIlc+ZNAdSQRjkfi+UDK7eKV
KGOlkcslroJO6rT3ruqx9L3hHtrM8dKQFgtRSaofB51HCyhNzmipbBHnLnKQrcf6
o8nn9OkP7F9NfbBE6xYIUCkgnv1lQbzeXsLLVuEKMW8bvZOmI7jTcthqnwzEIHj/
G4p+zPGgO+6Pzuhn47fxH+QZ0KPA8o2vx0DvOkZT6HEqG+EqpIoC/a7wD68n789c
K2NLCVb9oIGarPfhIdPV3QbrA5eXRRQ=
=QyNy
-----END PGP SIGNATURE-----

And you get this

Something went wrong while viewing the profile
The following error was reported:
Signature could not be read (readCleartextMessage: options.cleartextMessage must be a string)
Please see the documentation for help.

Schermata del 2024年11月04日 23-06-33

### What happened Use profile signature (https://keyoxide.org/sig), using your own text or the example one from documentation: ``` -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hey there! Here's a signature profile with proofs related to the DOIP project (https://doip.rocks). Verify this profile at https://keyoxide.org/sig proof=dns:doip.rocks proof=https://fosstodon.org/@keyoxide -----BEGIN PGP SIGNATURE----- iQHEBAEBCgAuFiEENjcgJSPnwTCat56Z7y3FgntEX0sFAl/7L0MQHHRlc3RAZG9p cC5yb2NrcwAKCRDvLcWCe0RfS3iYC/0QQqz2lzSNrkApdIN9OJFfd/sP2qeGr/uH 98YHa+ucwBxer6yrAaTYYuBJg1uyzdxQhqF2jWno7FwN4crnj15AN5XGemjpmqat py9wG6vCVjC81q/BWMIMZ7RJ/m8F8Kz556xHiU8KbqLNDqFVcT35/PhJsw71XVCI N3HgrgD7CY/vIsZ3WIH7mne3q9O7X4TJQtFoZZ/l9lKj7qk3LrSFnL6q+JxUr2Im xfYZKaSz6lmLf+vfPc59JuQtV1z0HSNDQkpKEjmLeIlc+ZNAdSQRjkfi+UDK7eKV KGOlkcslroJO6rT3ruqx9L3hHtrM8dKQFgtRSaofB51HCyhNzmipbBHnLnKQrcf6 o8nn9OkP7F9NfbBE6xYIUCkgnv1lQbzeXsLLVuEKMW8bvZOmI7jTcthqnwzEIHj/ G4p+zPGgO+6Pzuhn47fxH+QZ0KPA8o2vx0DvOkZT6HEqG+EqpIoC/a7wD68n789c K2NLCVb9oIGarPfhIdPV3QbrA5eXRRQ= =QyNy -----END PGP SIGNATURE----- ``` And you get this ``` Something went wrong while viewing the profile The following error was reported: Signature could not be read (readCleartextMessage: options.cleartextMessage must be a string) Please see the documentation for help. ``` 

j-simonson commented 2025年11月02日 20:12:43 +01:00

This bug (#205) was posted Nov 4, 2024, 04:09 PM CST.

Legacy signature profiles - Using GnuPG Doc was updated 2024年12月04日 07:29 UTC and states that:

"Legacy signature profiles are currently deprecated in favor of ASP profiles and may stop working in the future."

which is also reflected by commit 4c372e385b4b77a86a8aea0445cacbc4eb59bf21 for content/guides/signature-profile-gnupg.md from Sep 19, 2023, 10:10 AM CDT.

Suggesting issues such as this were anticipated.

This bug (#205) was posted Nov 4, 2024, 04:09 PM CST. [Legacy signature profiles - Using GnuPG Doc](https://docs.keyoxide.org/guides/signature-profile-gnupg/) was updated 2024年12月04日 07:29 UTC and states that: > _"Legacy signature profiles are currently deprecated in favor of ASP profiles and may stop working in the future."_ which is also reflected by commit 4c372e385b4b77a86a8aea0445cacbc4eb59bf21 for [content/guides/signature-profile-gnupg.md](https://codeberg.org/keyoxide/keyoxide-docs/commit/4c372e385b4b77a86a8aea0445cacbc4eb59bf21?files=content/guides/signature-profile-gnupg.md#diff-93e43d346e24083e04ec9765e669f851e0a50219) from Sep 19, 2023, 10:10 AM CDT. Suggesting issues such as this were anticipated.