[committee] Fwd: Your account has been locked

[Rufus Garton Smith]

Jeremy,

If someone changes the desktop background of another user's account to 
shock imagery and then logs out, and allows a member of committee and 
wheel to see him/her doing all this, I think that committee member is 
obliged to act. This is not something that anyone needs ANY warning for, 
it's obviouly something that one should not do.

As for locking the accounts of the people who left themselves logged in, 
as you mentioned in your email, this is a security risk. While this is not 
a major breach of our policy, it certainly is a breach. Therefore it would 
be unfair of me to lock Ashley's account (spook) and not lock Adrian's 
account (adrian). Particularly seeing as adrian is a wheel member and 
anyone could have used the machine to access locally cached private data, 
and a considerable amount of private data remotely.

Having just locked spook and adrian, I saw Sam (theodore) log off, which 
gave me yet another nice view of goatse as the desktop background. I asked 
him if that was his account, and he told me it was Scott's account 
(tinman), that they had been playing Team Fortress 2 on the same machine, 
and that he had done exactly the same thing as Ashley after Scott had 
left. Having only moments ago established the procedure for what to do in 
this situation, I was obliged to lock both their accounts.

By locking spook I was also obliged to lock adrian, theodore and tinman. I 
hope that clears everything up for you.

Regards,

Rufus


On Fri, 13 Nov 2009, Jeremy Cole wrote:

> So we are punishing people being trusting now? I can understand the security measures here, but seriously, locking peoples accounts for leaving themselves logged in? I thought that people in the room could be trusted to not create
> do really stupid things (Shocking someones background is not really stupid as by this logic rick rolling should carry the death penalty in UCC) This is setting a dangerous precedent for anyone who leaves the room even to go to the
> snack machine.
> I think locking of someones account needs to take more into account when the next committee meeting will be. For all we know over this break we may not have another meeting for two or three weeks, thus these people suffer lacking
> a UCC account for that amount of time. Yes if this was a serious issue then locking and handing it to committee would have been smart, but not in this case as (though i cant be completely sure) there was no warning for this and
> this is a pretty mundane issue where someone could have been told not to do it again first (and then a few more times)
> 
> my 2c
> 
> 
> On Fri, Nov 13, 2009 at 8:54 PM, Rufus Garton Smith <rvvs89 at ucc.gu.uwa.edu.au> wrote:
>       Adrian,
>
>       Your account has been locked for leaving your account logged in at UCC without locking it. I would not normally lock someone's account for this, but since I am also locking spook's account for abusing the account you
>       left logged in, it is only fair.
>
>       Regards,
>
>       Rufus
> 
> 
> 
> 
>