<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>No. GPSI generates a keypair and builds a related auth.defaults file on the fly. Because it will inevitably run jobs for multiple users, auth.defaults collisions will occur. I'm not doing anything to prevent this now, but need to.</div><div><br></div><div><br><div><div>On Aug 26, 2011, at 2:48 PM, Jonathan Monette wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I do not think so. Mike and I have brainstormed a couple work arounds for auth.defaults before. Such as using ssh master channels. Is this so the user could upload an auth.defaults on a per site basis during a run? <br><br>----- Reply message -----<br>From: "Thomas Uram" <<a href="mailto:turam@mcs.anl.gov">turam@mcs.anl.gov</a>><br>Date: Fri, Aug 26, 2011 1:38 pm<br>Subject: [Swift-devel] auth.defaults<br>To: "Mihael Hategan" <<a href="mailto:hategan@mcs.anl.gov">hategan@mcs.anl.gov</a>><br>Cc: "swift-devel" <<a href="mailto:swift-devel@ci.uchicago.edu">swift-devel@ci.uchicago.edu</a>>, "David Kelly" <<a href="mailto:dk0966@cs.ship.edu">dk0966@cs.ship.edu</a>><br><br><br>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? <br><br>Tom<br><br>On Aug 11, 2010, at 7:58 PM, Mihael Hategan wrote:<br><br>> On Wed, 2010-08-11 at 17:08 -0400, David Kelly wrote:<br>>> On Wed, Aug 11, 2010 at 4:18 PM, Mihael Hategan <<a href="mailto:hategan@mcs.anl.gov">hategan@mcs.anl.gov</a>><br>>> wrote:<br>>> <br>>> I don't think I understand what you mean by "per-host<br>>> auth.defaults".<br>>> <br>>> What I mean by that is, each configuration generated by swiftconfig<br>>> could have it's own unique auth.defaults file like it has it's own<br>>> sites.xml. Then you could run something like "swift<br>>> -auth.file /mypath/auth.defaults" rather than requiring it to be<br>>> stored in ~/.ssh.<br>> <br>> It's possible, but I don't think it's worth the effort. That file, like<br>> authorized_keys or known_hosts is not meant to contain frequently<br>> changing information, since passwords and usernanames are not generally<br>> a moving target (nor are host keys).<br>> <br>> <br>> _______________________________________________<br>> Swift-devel mailing list<br>> <a href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a><br>> <a href="http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel">http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel</a><br><br>_______________________________________________<br>Swift-devel mailing list<br><a href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a><br><a href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel">https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel</a><br><br><br></blockquote></div><br></div></body></html>