Grid and Cloud Computing Dr. Guy Tel-Zur

Today’s agenda UNICORE (see a separate presentation) AWS + Python (Boto) – ideas for projects… Hadoop (see a separate presentation) Home assignment #2

[security-announce] Globus Security Advisory : GridFTP acts as wrong user when mapped user doesn't exist 1 message Stuart Martin Thu, May 24, 2012 at 11:04 PM To: Globus Security Advisory : GridFTP acts as wrong user when mapped user doesn't exist Original issue date: May 24, 2012 Last revised: None Software affected: GridFTP Server Globus Toolkit releases 5.2.0, all servers are affected Globus Toolkit pre for *threaded* flavor servers only Overview: When a gridmap file is improperly configured with a valid user DN mapped to an invalid/nonexistent user account, the GridFTP server may grant access to the client under another account.

I. Description The GridFTP server was improperly checking the return values from the getpwnam-based GT wrapper functions. In the affected cases, the user authorization should have failed, but instead processing continues and the client is given access to another user account. II. Impact If a GridFTP server's gridmap file is improperly configured, a client with a valid user proxy and DN could get access to the files of another account. The actual account is most likely the final account in /etc/passwd, but there could be variations based on individual system implementations of the getpwnam_r() function. III. Solution This issue is addressed with an updated GridFTP Server package. For GT and GT 5.2.1, the update package is globus_gridftp_server Download and installation instructions are here: For GT 5.0.x, the update package is globus_gridftp_server-3.42.

About the Final Projects Where applicable: Related work Performance: – Scalability – Load balancing – Benchmarks Economic model Results (tables, graphs…)

Web cast tonight: “ Deployments with Eucalyptus and AWS CloudFormation ”