diff options
| author | Michał Górny <mgorny@gentoo.org> | 2025-10-19 17:53:32 +0200 |
|---|---|---|
| committer | Michał Górny <mgorny@gentoo.org> | 2025-10-23 20:18:59 +0200 |
| commit | 4751eb73831a1fd01f3dcc2caf4ac6911f93b474 (patch) | |
| tree | 76f78a84e73a06231bc7802bb241d7c6405cdd0b /dev-java/java-websocket/java-websocket-1.6.0.ebuild | |
| parent | 22bc2aebe9d9b1e6995607bb290abc8517f2f491 (diff) | |
| download | gentoo-4751eb73831a1fd01f3dcc2caf4ac6911f93b474.tar.gz gentoo-4751eb73831a1fd01f3dcc2caf4ac6911f93b474.tar.bz2 gentoo-4751eb73831a1fd01f3dcc2caf4ac6911f93b474.zip | |
verify-sig.eclass: Append a trailing newline to gpg --verify output
Explicitly append a trailing newline to the output stream created
by "gpg --verify", to ensure it always contains one. The FreePG
patchset to GPG corrects handling the trailing newlines in cleartext
signed messages, which means that GPG-created "incorrect" messages
no longer include a trailing newline character [1]. We are parsing
the checksum file via bash's "read" command that ignores the characters
after the final newline character, so we need to ensure that one is
always present after the ultimate checksum.
Adding an extra newline to vanilla GnuPG output causes no harm,
as the verification function will simply ignore the resulting empty
line.
[1] https://gitlab.com/freepg/gnupg/-/blob/a4e8d23439f1e101da3e335b3beab822be968d56/DIFF.md#handle-cleartext-signature-framework-csf-messages-correctly
Signed-off-by: Michał Górny <mgorny@gentoo.org>
Diffstat (limited to 'dev-java/java-websocket/java-websocket-1.6.0.ebuild')
0 files changed, 0 insertions, 0 deletions
