[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #21707 [Internal Services/Schleuder]: Please refresh teor's keys on schleuder



#21707: Please refresh teor's keys on schleuder
-----------------------------------------+--------------------------
 Reporter:  teor                         |          Owner:  hiro
     Type:  task                         |         Status:  reopened
 Priority:  Medium                       |      Milestone:
Component:  Internal Services/Schleuder  |        Version:
 Severity:  Normal                       |     Resolution:
 Keywords:                               |  Actual Points:
Parent ID:                               |         Points:
 Reviewer:                               |        Sponsor:
-----------------------------------------+--------------------------
Changes (by teor):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Replying to [comment:2 hiro]:
 > This is solved.

 Thanks Hiro!
 I can confirm that schleuder accepts my new signing subkey, and encrypts
 with my new encryption subkey. This is what I wanted.

 Two minor details:
 * The message was only encrypted with the newer encryption subkey, and not
 the old one. I think this happened because of a gpg2 bug/feature that only
 exported my newer encryption subkey. Do you know what schleuder does if
 there are two encryption subkeys?
 * I haven't checked my old signing key: I don't want to spam the list. Do
 you know if schleuder accepts any signing key or subkey?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21707#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs