Your message dated Fri, 2 Sep 2016 09:02:19 -0400
with message-id <[email protected]>
and subject line Re: Bug#751783: monkeysign: Provide means to add additional
options for gpg invocations
has caused the Debian Bug report #751783,
regarding monkeysign: Provide means to add additional options for gpg
invocations
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
751783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751783
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: monkeysign
Version: 1.1
Severity: wishlist
Dear Maintainer,
It would be great if monkeysign could allow to set options for location of gpg
or its secret keyring, for instance, which would allow non standard setups with
secret keyring not necessarily available with the default gpg config.
AFAICS, there's no way to sepcify such options to monkeysign.
Thanks in advance.
Best regards,
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'),
(500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages monkeysign depends on:
ii gnupg 1.4.16-1.1
ii python 2.7.6-2
ii python-pkg-resources 4.0.1-1
Versions of packages monkeysign recommends:
ii python-gtk2 2.24.0-3+b1
ii python-qrencode 1.01-3
ii python-zbar 0.10+doc-9+b1
ii python-zbarpygtk 0.10+doc-9+b1
monkeysign suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: tags -1 wontfix
On Mon, Jun 16, 2014 at 05:57:05PM +0200, Olivier Berger wrote:
> Package: monkeysign
> Version: 1.1
> Severity: wishlist
>
> Dear Maintainer,
>
> It would be great if monkeysign could allow to set options for location of
> gpg or its secret keyring, for instance, which would allow non standard
> setups with secret keyring not necessarily available with the default gpg
> config.
>
> AFAICS, there's no way to sepcify such options to monkeysign.
That is correct, and deliberate.
The problem with such options is that they would need to apply to *all*
GPG calls. Then you can quickly get into trouble because people could
start to be clever and pass stuff like `--default-keyring` or
`--interactive` (which breaks Monkeysign, see #723047).
We already have trouble enough with people specifying those options in
gpg.conf - I am not sure I want to allow more messing around like those.
But even worse: people could do really stupid stuff like passing
`--sign` or `--store`, `--no`, and so on... I am not sure I want to
provide such a foot-shooting device without a stronger use case.
In the use case you describe, it seems to me we would be better to port
Monkeysign properly to GPG 2.1, which handles private key operations
better without any additional configuration, rather than forcing the
user to try to configure monkeysign properly. Such a configuration would
be automatic and global, as opposed to specific to monkeysign and
error-prone.
Thanks for your feature request anyways, and sorry for the delay!
A.
signature.asc
Description: Digital signature
--- End Message ---
