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

Jody Harris jharris at harrisdev.com
Thu Feb 3 13:18:07 PST 2011


If it comes to that, I could set up a web interface to generate the "keys."
That would be easier than making shells available and worrying about
security.
----
- Think carefully.


On Thu, Feb 3, 2011 at 2:10 PM, Brad Rupp <bradrupp at gmail.com> wrote:

> On 2/3/2011 11:53 AM, Jody Harris wrote:
>
>> 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.
>>
>
> I'm with you now.  I was thinking total automation and that the gatekeeper
> was a process, not a person.
>
> Thinking out loud now, one or two of the gateway owners could create shell
> accounts on their gateway.  These shell accounts could access a script that
> creates/modifies the user's password.  This would be especially useful for
> those who don't have shell accounts.  Maybe everyone has shell accounts so
> this is not a big deal.  Anyway, just a thought.
>
>
> 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/f60f0be3/attachment-0001.html>


More information about the volunteergrid2-l mailing list