Is Debian Repeat Secure?

2010-09-19 Thread Martin Owens
Hey all, Building debs for ppa uses gpg and signs each source package build in two different places requiring the unlocking of the gpg key twice. I've been running a script which builds 4 packages for 3 ubuntu releases which comes to typing in my gpg passphraise 24 times in succession (more if I

Re: Is Debian Repeat Secure?

2010-09-19 Thread Chris Baines
Not a direct answer to your question, but, when I was using Ubuntu I had a script that I was using to make about 300 packages, I only had to type in my key once or twice. I have been trying to work out how to do it on Debian but so far have come up short. Chris On Sun, 2010-09-19 at 01:58 -0400,

Re: Is Debian Repeat Secure?

2010-09-19 Thread Russ Allbery
Martin Owens docto...@gmail.com writes: Building debs for ppa uses gpg and signs each source package build in two different places requiring the unlocking of the gpg key twice. I've been running a script which builds 4 packages for 3 ubuntu releases which comes to typing in my gpg

Re: Is Debian Repeat Secure?

2010-09-19 Thread Sascha Silbe
Excerpts from Russ Allbery's message of Sun Sep 19 10:01:58 +0200 2010: I use gpg-agent with a five minute timeout, which is long enough to let me sign a bunch of packages while I'm actively working (plus git tags and so forth) but short enough that I'm not too worried about an attacker taking

Re: Is Debian Repeat Secure?

2010-09-19 Thread Tony Houghton
On Sun, 19 Sep 2010 08:13:16 +0100 Chris Baines cbain...@gmail.com wrote: Not a direct answer to your question, but, when I was using Ubuntu I had a script that I was using to make about 300 packages, I only had to type in my key once or twice. I have been trying to work out how to do it on

Re: Is Debian Repeat Secure?

2010-09-19 Thread Martin Owens
On Sun, 2010-09-19 at 13:50 +0100, Tony Houghton wrote: I guess you already know you need to install gnupg-agent and one of the pinentry-* packages, but I found that Debian differs from Ubuntu by not enabling use-agent by default, so you have to edit ~/.gnupg/gpg.conf. Thanks for the info,