Quoting Lennart Poettering <[email protected]>:
I wonder if we can use --trustdb-name /dev/null
I think, no. I got a weird error using /dev/null
% strace -e file -o /tmp/blub1 gpg --no-options --no-default-keyring
--no-auto-key-locate --no-auto-check-trustdb --batch
--trust-model=always --keyring=/usr/lib/systemd/import-pubring.gpg
--verify ~/data/halde/signature.sig --trustdb-name /dev/null
trusty-server-cloudimg-amd64-root.tar.gz
gpg: Note: '--trustdb-name' is not considered an option
gpg: can't open signed data '--trustdb-name'
gpg: can't hash datafile: No such file or directory
% strace -e file -o /tmp/blub1 gpg --no-options --no-default-keyring
--no-auto-key-locate --no-auto-check-trustdb --batch
--trust-model=always --keyring=/usr/lib/systemd/import-pubring.gpg
--verify ~/data/halde/signature.sig
trusty-server-cloudimg-amd64-root.tar.gz
gpg: Signature made Sat 28 Feb 2015 02:07:02 CET using RSA key ID 7DB87C81
gpg: BAD signature from "UEC Image Automatic Signing Key
<[email protected]>" [unknown]
/pp
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
