User talk:Dispenser

Welcome to Tool Labs

Hello Dispenser, welcome to the Tool Labs project! Your request for access was processed and you should be able to login now via ssh at tools-login.wmflabs.org. To get started, check the help page and the migrating from the Toolserver page. You can also ask in our IRC channel at #wikimedia-labs ^connect or send an e-mail to our mailing list labs-l@lists.wikimedia.org – thank you, and have fun using Tools! Tim Landscheidt (talk) 01:02, 10 December 2013 (UTC)

Blocked

Since your account is being used to run non open-source software and you have refused or neglected to stop doing so despite having been warned, I have no choice but to disable your access to Labs at this time.

Individual tools you are listed as a maintainer of will be audited for compliance with our open-source policy before being reenabled. If you have data in your home or tool's homes that you wish to get a copy of, please notify any administrator of the tool labs project by email or on IRC.

— Coren/Marc ^(talk) 20:36, 27 August 2014 (UTC)

I removed the freeware/non-open source software like you asked me and was writing an email to legal asking for an exemption when you kicked me. The recent revelation that Labs will be officially a "Closed Source"/No-redistribute-required makes this ban even more absurd. I subsequently sent those emails and never received a response. Which is odd considering how you always needed to check legal with me about issues that were addressed on the mailing list months before.

The irony in all this? The tool that I got banned over was used to identify extraneous data in images which found encrypted RAR, zip, and 7z files that could've been warez or CP. We've also stumbled across PNGs stuff with Adobe Fireworks's proprietary layer data. —Dispenser (talk) 19:50, 10 April 2015 (UTC)

Where is that supposed "revelation" coming from? The requirement to have all code on Labs be open sourced remains, except for specifically delineated exceptions approved by Labs admin and WMF Legal – and for the record, none of those exist at this time. — Coren/Marc ^(talk) 17:08, 15 April 2015 (UTC)

He's probably referring to and confusing "being under an open source license but not publicly distributed" with "closed source". Anomie (talk) 13:17, 16 April 2015 (UTC)

Now compare this to what Ryan Lane's said last year, that entire thing should be forkable. Dispenser (talk) 22:17, 8 May 2015 (UTC)

Re-enabling your access to Tool Labs

Hi Dispenser. The Tool Labs admins are willing to rescind your block if you agree to the following conditions:

• You will review and strictly adhere to the Labs Terms of Use and Rules (especially the Prohibited Uses part).
• If you have any uncertainty about whether or not a particular use of Tool Labs would be in violation of the Terms of Use or Rules, you will seek approval by a Labs admin before pursuing it.

Failure to abide by these conditions will result in your Labs account being re-suspended. Please indicate whether or not you agree below. kaldari (talk) 19:36, 21 August 2015 (UTC)

@Kaldari: I agree to abide by the Labs Terms of use and Rules (which I helped create :-). If there any questions I will contact a Labs admin. —Dispenser (talk) 20:49, 21 August 2015 (UTC)

Hello Dispenser,

I have restored your shell access and your membership to the tools project given your agreement above. This does not include membership in any service group (tools) by default – you can ask any current maintainer for those as appropriate.

If you need to get access to old files or data, please file a Phabricator task with your specific request.

I'm going to reiterate what Kaldari said above and remind you that you need to abide strictly with the Terms of Use. If you have any doubt whether what you wish to do falls within a strict reading of the terms, consult with a Labs admin before going forward. Welcome back.

— Coren/Marc ^(talk) 13:43, 16 September 2015 (UTC)

Wiki Replica c1.labsdb to be rebooted Monday 2017-10-30 14:30 UTC

A tool you maintain is hosting data on labsdb1001.eqiad.wmnet (aka c1.labsdb). This server will be rebooted Monday 2017-10-30 at 14:30 UTC.

Normal usage of the *.labsdb databases should experience only limited interruption as DNS is changed to point to the labsdb1003.eqiad.wmnet (aka c3.labsdb). The c1.labsdb service name will not be updated however, so tools hardcoded to that service name will be interrupted until the reboot is complete.

There is a possibility of catastrophic hardware failure in this reboot. There will be no way to recover the server or the data it currently hosts if that happens. Tools that are hosting self-created data on c1.labsdb will lose that data if there is hardware failure. If you are unsure why your tool is hosting data on c1.labsdb, you can check the database and table names at https://tools.wmflabs.org/tool-db-usage/.

This reboot is an intermediate step before the complete shutdown of the server on Wednesday 2017-12-13. See Wiki Replica c1 and c3 shutdown for more information. --BryanDavis 00:22, 28 October 2017 (UTC)

Wiki Replica c3.labsdb to be shutdown Wednesday 2017-12-13

A tool you maintain is hosting data on labsdb1003.eqiad.wmnet (aka c3.labsdb). This server will be taken out of service on Wednesday 2017-12-13.

Normal usage of the *.labsdb databases should experience only limited interruption as DNS is changed to point to the new Wiki Replica cluster. The c3.labsdb service name will not be updated however, so tools hardcoded to that service name will be interrupted until they are updated to use a new service name.

Tools that are hosting self-created data on c3.labsdb will lose that data if it is not migrated to tools.db.svc.eqiad.wmflabs (also known as tools.labsdb). If you are unsure why your tool is hosting data on c3.labsdb, you can check the database and table names at https://tools.wmflabs.org/tool-db-usage/ or phab:P6313.

Please see Wiki Replica c1 and c3 shutdown for more information. --BryanDavis 20:36, 15 November 2017 (UTC)

Formal warning of censure

Your 2017-11-17T21:08 UTC decision to publicly disclose a security vulnerability in file system level permissions affecting other user accounts in the Toolforge platform via the #wikimedia-cloud ^connect IRC channel was not a responsible disclosure. This is interpreted as a harmful activity and disruptive or abusive activity under the Wikitech:Labs Terms of use. You have previously acknowledged that you understand the Terms of Use and agree to abide by them. Please understand that this action was a serious breach of the trust that Kaldari and others have placed in you and your ability to collaborate in a positive manner with both the Cloud Services administrators and the larger Wikimedia technical community. There will be a zero tolerance policy for further intentional disruptions of the operations of the platforms or the communities that use them. --BryanDavis (talk) 22:00, 17 November 2017 (UTC)

@BryanDavis: You were informed 24 hours prior. Additionally, I mentioned on 2017-11-06 that /home/stuem007 was world writable (clearly visible in my colorized ls and immediately corrected). I mentioned there should be an automated script for detection and I was publicly informed there wasn't and it caused issues before in a "great delete". I wasn't told until today to file a separate security tickets. --Dispenser (talk) 22:52, 17 November 2017 (UTC)

@Dispenser: Through what channel was I informed 24 hours prior? I agree that you did previously publicly disclose a similar security issue on 2017-11-06. I'm sorry that you took my lack of publicly freaking out at that occurrence of a similar breach of trust as license to perform a second and larger irresponsible disclosure. --BryanDavis (talk) 23:52, 17 November 2017 (UTC)

Thanks

For all you have done to support the projects. All the best: Rich Farmbrough, 15:01, 3 August 2024 (UTC).