[volunteergrid2-l] mod_proxy protected gateways -- common user file

[Jody Harris]

The "gatekeeper" would remove them from the "key aggregator."

I was thinking that the "gatekeeper" would be one or two individuals.

and that the gatekeeper would aggregate the keys into a single file that the
other nodes would download. That way, only the gatekeepers would need to
keep track of who's in and who's out of the list.

does that even make sene? I'm going to go eat lunch and see if my writing
skills improve with caloric intake.

jody
----
- Think carefully.


On Thu, Feb 3, 2011 at 11:47 AM, Brad Rupp <bradrupp at gmail.com> wrote:

> On 2/2/2011 8:54 PM, Jody Harris wrote:
>
>> I thought of that, too.... :-)
>>
>> Another thought:
>> If each person could create their own entry in the user table, then each
>> user's password would be always confidential.
>>
>>   - Each user could publish their entry to a mutable file in the grid,
>>   - then supply the capability to the "gatekeeper."
>>   - The gatekeeper could add the information to the cronjob
>>   - The gatekeeper_cronjob would generate the central file.
>>
>
> One other thought on this.  How will we handle users that leave the grid.
>  Say I leave grid and you don't want me accessing the public gateways
> anymore.  As it stands right now, each gateway operator would need to remove
> me from their user file.  Maybe that is good enough given the few users we
> will have.  However, we do need to think about this.
>
> Brad
>
> _______________________________________________
> volunteergrid2-l mailing list
> volunteergrid2-l at tahoe-lafs.org
> http://tahoe-lafs.org/cgi-bin/mailman/listinfo/volunteergrid2-l
> http://bigpig.org/twiki/bin/view/Main/WebHome
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/cgi-bin/mailman/private/volunteergrid2-l/attachments/20110203/0f612404/attachment.html>