Bruce, thanks for the hook info, I didn't think of checking there. I'll put that into use now. Is it possible to specify where the user's key directory is located (specifically on Windows)? If a user is using a local profile but has their "my documents" relocated via a group policy, their key files will reside on the local machine (which might not be what they expect and won't know to back that up).
Thanks! -John -----Original Message----- From: [EMAIL PROTECTED] .org [mailto:monotone-devel-bounces+john-keyword-monotone.4a150f=coolpeople.u [EMAIL PROTECTED] On Behalf Of Bruce Stephens Sent: Sunday, December 04, 2005 3:00 PM To: [email protected] Subject: [Monotone-devel] Re: Multiple private keys in 0.24 "John W. Terrell" <[EMAIL PROTECTED]> writes: > Hi all, I've seen prior posts about multiple private key handling issues > with the way 0.24 now handles them and I wonder if it might be a > solution to have each database have a var that indicates what the > current "private" key is. I check into multiple databases using > different private keys (different email addresses - this is by design) > and it's a bit of a pain to have to specify the -k switch now when I'm > commiting/syncing, etc. This database var would only have the current > private key's ID (not the private key itself) so I wouldn't think > there'd be any security issues (I could be wrong). Currently you can put a key id into the MT/options file in a working copy. I'm not sure if that's documented, but it's been mentioned on the mailing list several times. You can also define a get_branch_key hook, which gives a key to be used for a given branch. Aren't those better than having it in a database? _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
