, 2004-09-15
Academic institutions who have to add, manage, and secure thousands of new users within a period of just a few days face political and social issues on top of the immense technical ones.
Expand all |
Post comment
Academia Headaches
2004-09-16
Anonymous (3 replies)
Anonymous (3 replies)
grow up
2004-09-17
Anonymous (1 replies)
Anonymous (1 replies)
another vote for open-sourcing the perl code
2004-09-17
Anonymous (1 replies)
Anonymous (1 replies)
another vote for open-sourcing the perl code
2004-09-18
Anonymous (1 replies)
Anonymous (1 replies)

It is important to notice that students own pc's are their property, so faculty have no right to take away admin privileges, or install software. What can be done though is to define a set of requirements for obtaining access, and give the users the ability to maintain their system.
When a computer is compromised, the admin can rightfully shut off connection, the user have no right to complain because the he should have known better. I have practiced such a policy with success, although the response time could be hours depending on when the infection occured because we relied on manual intervention. In the other end of the scale I complained to an ISP that did absolutely nothing for two months allowing about 700.000 virus infected mails to be send from their client.
Really, it is a matter of pragmatically solving a problem that isn't yours. Access is not a right, it's a privilege and as such it should be treated with care or it is taken away.
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/columns/267/28484#28484