[Swift-devel] auth.defaults

[Thomas Uram]

In a portal scenario, where the portal is executing jobs on behalf of users and, therefore, shuffling identities on the backend, this functionality would be useful. Has work on this progressed at all? 

Tom

On Aug 11, 2010, at 7:58 PM, Mihael Hategan wrote:

> On Wed, 2010-08-11 at 17:08 -0400, David Kelly wrote:
>> On Wed, Aug 11, 2010 at 4:18 PM, Mihael Hategan <hategan at mcs.anl.gov>
>> wrote:
>> 
>>        I don't think I understand what you mean by "per-host
>>        auth.defaults".
>> 
>> What I mean by that is, each configuration generated by swiftconfig
>> could have it's own unique auth.defaults file like it has it's own
>> sites.xml. Then you could run something like "swift
>> -auth.file /mypath/auth.defaults" rather than requiring it to be
>> stored in ~/.ssh.
> 
> It's possible, but I don't think it's worth the effort. That file, like
> authorized_keys or known_hosts is not meant to contain frequently
> changing information, since passwords and usernanames are not generally
> a moving target (nor are host keys).
> 
> 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel