Your message dated Mon, 05 Dec 2016 20:05:56 -0500
with message-id <[email protected]>
and subject line Re: [pkg-gnupg-maint] Bug#835045: Bug#835045: gnupg: cannot 
edit my    key: "secret key parts are not available"
has caused the Debian Bug report #835045,
regarding gnupg: cannot edit my key: "secret key parts are not available"
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.)


-- 
835045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835045
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg
Version: 1.4.20-6
Severity: important

Hello!

I'm trying to update my gpg key expiry date, but am having
difficulties:

polya:~ $ gpg --edit-key 0x59D03CC92BA0FEAE
Secret key is available.

pub  4096R/0x59D03CC92BA0FEAE  created: 2014-10-29  expires: 2016-10-28  usage: 
SC
                               trust: ultimate      validity: ultimate
                               sub  4096R/0x14A58BD97483A28B  created: 
2014-10-29  expires: 2016-10-28  usage: E
                               sub  4096R/0x695C429316C07BFE  created: 
2014-10-29  expires: 2016-10-28  usage: S
                               [ultimate] (1). Julian Gilbey 
<[email protected]>
                               [ultimate] (2)  Julian Gilbey <[email protected]>
                               [ultimate] (3)  Julian Gilbey 
<[email protected]>
                               [ultimate] (4)  Julian Gilbey <[email protected]>

gpg> expire
Changing expiration time for the primary key.
gpg: WARNING: no user ID has been marked as primary.  This command may
              cause a different user ID to become the assumed primary.
Please specify how long the key should be valid.
         0 = key does not expire
      <n>  = key expires in n days
      <n>w = key expires in n weeks
      <n>m = key expires in n months
      <n>y = key expires in n years
Key is valid for? (0) 2y
Key expires at Tue 21 Aug 2018 17:33:49 BST
Is this correct? (y/N) y
gpg: secret key parts are not available
gpg: make_keysig_packet failed: general error

gpg>

And yet I do have my secret key available; "toggle" shows it quite
happily, for example.

So I'm a little stymied.  It might be that gpg2 will fix this issue,
but maybe not.

Any ideas?

Thanks,

   Julian

--- End Message ---
--- Begin Message ---
On Mon 2016-08-22 17:46:08 -0400, Julian Gilbey wrote:
> On Mon, Aug 22, 2016 at 12:23:09PM +0200, Werner Koch wrote:
>> On Sun, 21 Aug 2016 18:36, [email protected] said:
>> 
>> > gpg: secret key parts are not available
>> 
>> > And yet I do have my secret key available; "toggle" shows it quite
>> > happily, for example.
>> 
>> I guess you took your primary key offline (replaced by a stub key) or
>> you are using smartcard based keys.  Use gpg -K to check the key.  For
>> example an old copy of my key listed with gpg 1.4:
>
> Hi Werner,
>
> Ah, thanks, that would be it!  Now I have to go and locate my primary
> key (having had no recollection of doing this...).
>
> Feel free to close this bug report.

closing as requested.  Thanks for your earlier report!

        --dkg

--- End Message ---

Reply via email to