| 1 |
On Thu, Mar 14, 2013 at 10:32:30PM -0400, Michael Mol wrote: |
| 2 |
> > As to how to accomplish this, it's either a throwaway sig, or poking the |
| 3 |
> > agent protocol directly. |
| 4 |
> The only trouble with that is if the agent is configured to only unlock |
| 5 |
> keys for limited periods of time, then your initial check might catch |
| 6 |
> the agent when the key is still unlocked, but your subsequent call to |
| 7 |
> GPG comes after the timeout. I ran into this while trying to set up |
| 8 |
> automated signing of debian packages I was building. |
| 9 |
So Debian has a test-gpg function already? Do you know where in their |
| 10 |
codebase it is? |
| 11 |
|
| 12 |
> All it really means, in a practical procedural sense, is that you need |
| 13 |
> to allow yourself a way to roll back anything you've been doing if that |
| 14 |
> later check fails. |
| 15 |
I think we'd do: |
| 16 |
- All repoman checks |
| 17 |
- initial file editing |
| 18 |
if two-phase commit: |
| 19 |
- test gpg |
| 20 |
- commit1 |
| 21 |
- gpg sign |
| 22 |
- commit2 |
| 23 |
if one-phase commit: |
| 24 |
- gpg test |
| 25 |
- gpg sign |
| 26 |
- commit1 |
| 27 |
|
| 28 |
Unless commit1 took a really long time, the interval between the gpg |
| 29 |
calls should be very small. |
| 30 |
|
| 31 |
-- |
| 32 |
Robin Hugh Johnson |
| 33 |
Gentoo Linux: Developer, Trustee & Infrastructure Lead |
| 34 |
E-Mail : robbat2@g.o |
| 35 |
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 |
Archives