Re: Bug#840669: [pkg-gnupg-maint] Bug#840669: Bug#840669: Beware of leftover gpg-agent processes

2016-10-19 Thread Werner Koch
On Fri, 14 Oct 2016 21:47, d...@fifthhorseman.net said: >> In a new temp directory do: >> >> GNUPGHOME=$(pwd) gpg-agent --daemon gpg . >> >> Or whatever you want to run under gpg-agent's control. This has been >> there for ages. > > fwiw, this doesn't work (and actually returns an error) if

Re: [pkg-gnupg-maint] Bug#840669: Beware of leftover gpg-agent processes

2016-10-14 Thread Werner Koch
On Fri, 14 Oct 2016 19:17, ijack...@chiark.greenend.org.uk said: > authorisations, if the user types in a passphrase) have a lifetime > limited by that of the gpg process which started the agent. In a new temp directory do: GNUPGHOME=$(pwd) gpg-agent --daemon gpg . Or whatever you want to

Re: [pkg-gnupg-maint] Beware of leftover gpg-agent processes

2016-08-06 Thread Werner Koch
On Sat, 6 Aug 2016 08:24, p...@debian.org said: > BTW, does this make parcimonie obsolete? I noticed that dirmngr We plan to add similar fucntionality to dirmngr but that has not yet been done and I am not sure whether we will have it for 2.2. Shalom-Salam, Werner -- Die Gedanken sind

Re: Bits from keyring-maint

2011-04-06 Thread Werner Koch
Hi, I do not think that it is a good idea to push for 4k RSA keys! You gain nothing from it except for slowness on small devices. Debian is used on a lot of small devices. Further DDs are strongly represented in the WoT and thus many keyrings will increase in size and checking all the

Re: Revival of the signed debs discussion

2003-12-03 Thread Werner Koch
hash on the remote machine is not the cleanest solution, so I have to come up with a better way. Werner -- Werner Koch [EMAIL PROTECTED] The GnuPG Expertshttp://g10code.com Free Software Foundation Europe

Re: Revival of the signed debs discussion

2003-12-03 Thread Werner Koch
On Wed, 3 Dec 2003 13:26:02 +0100, Matthias Urlichs said: I'm also a bit concerned about MitM attacks; the hash-or-whatever which Obviously you can do this only using a secure channel. the local side is supposed to sign should probably be encrypted with the signer's public key, otherwise I