[WikiEN-l] SlimVirgin and CheckUser leaks

[Jon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Katz wrote:
> The thread at
> http://en.wikipedia.org/wiki/Wikipedia:Administrators%27_noticeboard/Incidents/Tony_Sidaway#Break:_checkuseris
> very disturbing. SlimVirgin seems to have inside knowledge from the
> Checkuser Logs of which users Lar has been running checks on. The only way
> she could have obtained this knowledge is if there is either a leak on the
> Checkuser-L list or if someone with access to the Checkuser logs told her.
> 
> What is being done to plug this leak? If it came from a CheckUser or
> developer that person should be sacked immediately.
> 
> SV should be required to say how she got this information and if she refuses
> she should be blocked until she becomes co-operative.
> 
> This sort of security breach is completely unacceptable and intolerable.
> 
> Dave
> _______________________________________________
> WikiEN-l mailing list
> WikiEN-l at lists.wikimedia.org
> To unsubscribe from this mailing list, visit:
> https://lists.wikimedia.org/mailman/listinfo/wikien-l

Yeah...... no.


There is a process for this, it is not however, blocking an editor until
they give us the information we want.  Inquisition?  This is not our values.

Instead...

Suspicion of abuses of CheckUser should be discussed by each local wiki.
On wikis with an approved ArbCom, the ArbCom can decide on the removal
of access. On wikis without an approved ArbCom, the community can vote
removal of access. Removal can only be done by Stewards. A Steward may
not decide to remove access on their own, but can help provide
information necessary to prove the abuse (such as logs). If necessary,
and in particular in case of lack of respect towards the privacy policy,
the Board of Wikimedia Foundation can be asked to declare removal of
access as well.

Complaints of abuse of CheckUser or privacy policy breaches may also be
brought to the Ombudsman committee.


3 options

Discussion
RFARb
Privacy Ombudsman.


Nowhere do I see "block the user till they speak".

Thanks,
Jon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiCNcsACgkQ6+ro8Pm1AtXEKACfUpY6Pa+T9CWfrXGagkKZIZfp
ayAAoKp2LFcWvh/1rvKQcr6/ZYZR8MMn
=i+fs
-----END PGP SIGNATURE-----