On Wed 2018-09-05 09:39:31 +0200, Kristian Fiskerstrand wrote:
> On 9/4/18 6:10 PM, Daniel Kahn Gillmor wrote:
>> or do you mean something else?
>
> without DISPLAY env var, qt version automatically falls back to curses
> variant despite the argument
>
> kristianf@ares ~ $ unset DISPLAY
>
On 05/09/18 16:29, Fiedler Roman wrote:
> Apart from that, is not the
>
> [GNUPG:] VALIDSIG 25CE8B1D52A5B231543F8D660EE7BE094144A67F 2018-09-05
> 1536157493 0 4 0 1 8 00 25CE8B1D52A5B231543F8D660EE7BE094144A67F
>
> more suited for checking?
Generally: no. It just indicates the signature is
> Von: Peter Lebbing [mailto:pe...@digitalbrains.com]
>
> On 05/09/18 10:45, Fiedler Roman wrote:
> > * Decrypt and verify with gpg1 on receiver side:
> >
> > /usr/bin/gpg1 --no-options --homedir Receiver --no-default-keyring --
> keyring Sender/SenderKey.pub --lock-never --trust-model always
On 05/09/18 15:50, Fiedler Roman wrote:
> @Peter: thanks for looking at it more closely. There might be quite some
> sleeping
> dogs in semi/fully-automated gpg2 operation.
It's just one bug, if even, depending on my understanding of the
mechanism. One swallow does not a summer make; such
On 05/09/18 15:50, Fiedler Roman wrote:
> The "--pinentry-mode" is here only to make gpg-agent/gpg2 happy to get rid
> of tty-related errors. The batch commands do not request any passphrase
> to be set, so it should never be read
Can you point to the documentation where it says so? Because the
> Von: Peter Lebbing [mailto:pe...@digitalbrains.com]
> Gesendet: Mittwoch, 5. September 2018 15:21
> An: Fiedler Roman ; gnupg-users@gnupg.org
> Betreff: Both correct and surprising non-interactive gen-key (was: How to fix
> "ERROR key_generate 3355453" / "GENKEY' failed: IPC call has been
>
On 31/08/18 19:11, Fiedler Roman wrote:
> ['/usr/bin/gpg', '--homedir', '/tmp/tmp-3abk6l8', '--with-colons',
> '--status-fd', '2', '--pinentry-mode', 'loopback', '--batch', '--gen-key',
> '--command-fd', '0']
It is unclear where the passphrase is supposed to come from... so I
think it's
On 05/09/18 10:45, Fiedler Roman wrote:
> * Decrypt and verify with gpg1 on receiver side:
>
> /usr/bin/gpg1 --no-options --homedir Receiver --no-default-keyring --keyring
> Sender/SenderKey.pub --lock-never --trust-model always --batch
> --display-charset utf-8 --status-fd 2 --decrypt
What does an unencrypted, signed message mean to you? Because when we're
talking about the benefits or operation model of a hypothetical
"throw-keyid" option for signatures, that's what we are discussing.
Anything about encrypted messages is not relevant, since the signature
is inside the
> Von: Peter Lebbing [mailto:pe...@digitalbrains.com]
>
> On 05/09/18 11:27, Fiedler Roman wrote:
> > Sorry, but you are completely off here.
>
> If there are six people I am actually interested in, and I know all
> their public keys,
How will you know them? I will not tell you the keys, nor
On 9/5/18 9:39 AM, Kristian Fiskerstrand wrote:
> without DISPLAY env var, qt version automatically falls back to curses
> variant despite the argument
Wrote too quickly there; This is actually wrong, it never actually falls
back to curses, it just fails.
--
On 05/09/18 11:27, Fiedler Roman wrote:
> Sorry, but you are completely off here.
If there are six people I am actually interested in, and I know all
their public keys, checking if one of them signed a message with a
hypothetical "throw-keyid" takes me at most six trial verifications,
using their
> Von: Werner Koch [mailto:w...@gnupg.org]
>
> On Wed, 5 Sep 2018 10:45, roman.fied...@ait.ac.at said:
>
> > No, this is a signed AND encrypted message. Can gpgv only be
> > used to verify signatures on signed-only but not signed AND
> > encrypted messages, maybe due to encrypt AFTER sign
> Von: Werner Koch [mailto:w...@gnupg.org]
>
> On Tue, 4 Sep 2018 18:31, roman.fied...@ait.ac.at said:
>
> > At which byte offset should I find the signer key fingerprint?
>
> That is an encrypted message and thus can you seen the the signature.
That is good, one more issue not having to care
On Tue, 4 Sep 2018 18:31, roman.fied...@ait.ac.at said:
> At which byte offset should I find the signer key fingerprint?
That is an encrypted message and thus can you seen the the signature.
>> Leaving this out would not help because it is easy to
>> figure out the key by trial verification
On Wed, 5 Sep 2018 10:45, roman.fied...@ait.ac.at said:
> No, this is a signed AND encrypted message. Can gpgv only be
> used to verify signatures on signed-only but not signed AND
> encrypted messages, maybe due to encrypt AFTER sign scheme?
Correct. The signature is encrypted and thus it
> Von: Peter Lebbing [mailto:pe...@digitalbrains.com]
> ...
> $ gpgv --keyring ./key.gpg data.gpg
>
> > Splitting up the message gives me
> >
> > 01-001.pk_enc
> > 02-018.encrypted_mdc
>
> This is an encrypted message. gpgv can't do anything with it.
No, this is a signed AND encrypted
> Von: Peter Lebbing [mailto:pe...@digitalbrains.com]
>
> On 04/09/18 18:31, Fiedler Roman wrote:
> > /usr/bin/gpgv --status-fd 2 --homedir /proc/self/fd/nonexistent --keyring
> sign.pub /proc/self/fd/0
>
> You missed my point. You are not including a slash in the keyring
> argument, so gpgv is
On 9/4/18 6:10 PM, Daniel Kahn Gillmor wrote:
> or do you mean something else?
without DISPLAY env var, qt version automatically falls back to curses
variant despite the argument
kristianf@ares ~ $ unset DISPLAY
kristianf@ares ~ $ /usr/bin/pinentry-qt4 --display :0
(pinentry-qt4:6370):
19 matches
Mail list logo
