With great power comes great responsibility ... works everywhere :-)
Thank you Aaron!, just wanted to learn if I had missed out any possibilities as
well.
Amit
-Original Message-
From: Aaron Peeler [mailto:fapee...@ncsu.edu]
Sent: Tuesday, July 19, 2011 8:15 AM
To: vcl-dev@incubator.apache.org
Subject: Re: VCL Risk for Collaborators With Permissions to manage
Images
Hello Amit,
There's always risks, but I think it depends on the situation and the
relation with the other party.
You can add them as a non-root or non-admin user and always monitor
their usage, also explain to them that they must follow your existing
computer use policies or there access will be revoked(if feasible).
This usually works for us.
Hope this helps,
Aaron
On Mon, Jul 18, 2011 at 5:22 PM, Kumar, Amit H. ahku...@odu.edu
wrote:
Hello,
Don't know if this has been answered already in the forum...
What are the risks? If we were to let collaborators external to the
university have admin access to a reservation made on a VCL resource
either vmware or baremetal?
Any thoughts? Any way to lock him out?
Please advise!
Regards,
Amit
--
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
--
BEGIN-ANTISPAM-VOTING-LINKS
--
Teach CanIt if this mail (ID 530743466) is spam:
Spam:
https://www.spamtrap.odu.edu/b.php?i=530743466m=bde068cdea4et=2011071
9c=s
Not spam:
https://www.spamtrap.odu.edu/b.php?i=530743466m=bde068cdea4et=2011071
9c=n
Forget vote:
https://www.spamtrap.odu.edu/b.php?i=530743466m=bde068cdea4et=2011071
9c=f
--
END-ANTISPAM-VOTING-LINKS