Control: tags -1 +moreinfo
On 2013-09-15 15:28:23, Markus Teich wrote:
> Heyho,
>
> I have 'interactive' set in my gpg.conf.
...why?
I have never even used this setting myself. I had to look it up in the
manpage to figure out what it was. I though it was the opposite of
`--batch`, which would explain why monkeysign would have trouble, but it
is actually:
-i
--interactive
Prompt before overwriting any files.
Oh well.
GPG rarely writes any files itself.. why do you have that option
hardcoded in gpg.conf? It is not in the sample gpg.conf file I have in
my home directory.
> This leads to monkeysign failing to import the key, that should be signed.
I'm really curious to hear more about how it fails - I can't think of
anywhere we make gpg write files...
Can you provide an error message or a backtrace, or a full run with `--debug`?
> When i disable interactive mode in gpg.conf, monkeysign works as intended.
> A possible solution may be to remove the interactive setting from the
> temporary
> keyrings configuration on initialization.
I would rather not have to start messing around parsing (and
rewriting!!) gpg.conf, to be honest. In #721599, there was a discussion
on how to *read* options in a relatively portable way:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721599#71
... but *writing* to that file is more complicated. As far as I know,
gpg doesn't garantee that the file format will not change and usually
encourages people to not mess around the data structures in the back
like this.
I am tempted to mark this as "wontfix" because it's such an odd
configuration for me, but I could be convinced otherwise!
Thanks for your bug report...
A.
--
It is the greatest of all mistakes to do nothing because you can only
do little. Do what you can.
- Sydney Smith
