Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of Kostas Georgiou said:
> From what i remember it's date, uid, file, host. The uid info
> is useless
> so the info is not enough unfortunately, a WN can run more
> than one job at a time and there is no real limit on the CE.
What scenario are you trying to cover? Usually there are no more than
two jobs per WN so that info will get it down to either one or two
users, and in practice that's probably enough, especially given that the
rogue user (or stolen proxy) has probably done other things. If you want
to be able to prove legal liability nothing we have at the moment is
likely to be good enough, as we've discussed before.
If it's a question of undoing damage, i.e. remove all files modified
using a given proxy in a given time window, then you might have to
quarantine files written by other users to be safe.
Another point is that if people wanted posix access it's far more
likely to be for read than write, indeed with the standard lcg tools you
can only write files with gridftp, so having read-only rfio would
potentially be an interim solution.
There's also a more general point. Jobs on WNs can make arbitrary
outgoing connections, so if a job is part of a DDOS attack or does
something bad to an external site you have exactly the same problem, you
know which host it came from but not which job. On the face of it you'd
have to log all IP connections from every WN to really have precise
traceability - that's a lot of logs ...
Stephen
|