On 12/20/10 3:42 PM, Greg Troxel wrote: > > Even if I could do a 'tahoe show-usage' and get something that is > > blocks pubkey > > and then a 'tahoe remove-all offending-pubkey' as a server admin that > would be a great start.
Yeah, that should be part of Phase 1. I've been thinking of a web interface for it, but having a CLI command to make changes would be a good idea too. The 'blocks pubkey' line could also include a (self-provided) nickname for each key, and should eventually have a (provided-by-you) petname for each. > The WOT is what lets me as a server operator know that some pubkey > actually belongs to someone that I want to let store shares. People > who are into tahoe are probably also doing pgp, and one can use the > existing checked keys for mails to bootstrap the tahoe access keys, > distribute the introducer URI, etc. Hmm. Maybe a tahoe utility which gives you a message (containing some accounting identifiers) and asks you to PGP-sign it, then a corresponding utility on the receiving end which invokes PGP to check the signature before updating the tahoe.cfg? In general, yeah, Tahoe can reasonably do accounting up to the level of a pubkey, but then external tools or contrib/* utilities are probably the best way to associate those pubkeys with actual people. >> But take a look at the proposal and see what you think.. maybe >> there's some easy-enough way to leverage an existing format. > > Is this in a file/ticket/web-page, or did you mean your recent long > email? My email. We have a ticket that's close to this (#666), but I haven't yet updated it with the current discussion. cheers, -Brian _______________________________________________ tahoe-dev mailing list [email protected] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
