spigot-anti-piracy-backend
Advanced tools
I'm sad that such a project is existing.
Since 2011 I'm providing the community with a lot of free CraftBukkit plugins.
Over one and a half million downloads in total. That is a huge number.
Nevertheless the community is in some points an unkind one.
It does not matter how much spare time you spent, the update was never fast enough. And complaining is always easier than to say "thank you!".
With the premium plugin solution, Spigot offers the developers a way to the get something back for their work. And in general a lot cheaper than hiring a private plugin developer. When you see your plugin only one week after the initial release on sites that offer leaked plugins, it's frustrating.
That's why I decided to make my own validation service - to blacklist the leaker is often a lot faster than sending DMCA requests to One-Click-Hosters (OCH).
The Spigot built in piracy protection is known and easy to remove. There is a way to receive the user id of the buyer in your code. Please contact me on SpigotMC, I'd like to make the method not total publicly accessible (although it is when you dig enough).
Once you retrieved the user id you can make a POST request the URL where you service runs. In the body, include the following information:
user_id=foobar
(userId works, too)
An example Java implementation can be found in docs/.
The service is only accepting POST, no GET. You receive a JSON with either blacklisted true or false:
{
"blacklisted": true
}
Ensure that your server you wish to run the piracy backend with is running at least Node 10 LTS
$ npm install -g spigot-anti-piracy-backend
(Optionally without the global flag)
$ git clone https://github.com/timbru31/spigot-anti-piracy-backend.git
$ cd spigot-anti-piracy-backend
$ npm install
$ npm run watch
You need to manually maintain a blacklisted users file. I'd recommend a simple text file, with one blacklisted user id per line.
Just use
$ npm run start
Configuration via environment variables
| Environment Variable | Default | Description |
|---|---|---|
| PORT | 3000 | Port to run the app on |
| BLACKLISTED_USERS_FILE | ./banned_users.txt | Blacklist file |
| LOG_FILE | ./request.log | Log file for requests |
| PROXY | false | Tells Koa to run on proxy mode, for support for X-Forwarded Headers |
| JSON_LOG | true | Logs to the file in a JSON format, disable for human readable output |
It's up to you, if you would like to spin the service up with e.g. a linux start script.
For example here is an upstart script which runs the script as a non privileged user.
You can read more about upstart here
(Script was inspired by http://technosophos.com/2013/03/06/how-use-ubuntus-upstart-control-nodejs-forever.html)
description "Spigot Anti-Piracy Backend Server"
author "timbru31"
# Start up when the system hits any normal runlevel, and
# shuts down when the system goes to shutdown or reboot.
start on filesystem or runlevel [2345]
stop on runlevel [06]
setuid example
# The user's home directory
env HOME=/home/example
env PORT=3005
env BLACKLISTED_USERS_FILE=/home/example/banned_users.txt
# automatically respawn
respawn
respawn limit 99 5
# Send error messages to the console. Useful for debugging.
#console output
script
spigot-anti-piracy-backend
end script
You can watch the app.ts for file changes via the task
$ npm run watch
It uses Nodemon to watch for file changes and re-starts the server if any are found.
Test are run with Mocha via
$ npm run test
The code is linted using TSLint.
Keep the warnings to zero. :smile:
Please make sure they all pass and add new ones when you develop new stuff! :smile:
Please follow the commitizen style when making new commits!
Since this is a blacklist solution, a planned future is to validate the supplied user id against the buyers of the premium plugin. Only when it's on the list, the plugin is allowed to start (as long, as the user is not blacklisted).
The following document query can be used to retrieve an array of all user id's who bought the plugin:
let buyers = Array.from(
document.querySelector('.memberList').querySelectorAll('a.username')
);
buyers.forEach((elem, index, arr) => {
arr[index] = parseInt(
elem.pathname.replace(/\/members\/[-_a-zA-Z0-9]+\./, '').replace('/', '')
);
});
Built by (c) Tim Brust and contributors. Released under the MIT license.
2.0.0 (2019-06-12)
<a name="1.2.1"></a>
FAQs
A koajs application to blacklist leaked plugins
The npm package spigot-anti-piracy-backend receives a total of 14 weekly downloads. As such, spigot-anti-piracy-backend popularity was classified as not popular.
We found that spigot-anti-piracy-backend demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A Stanford study reveals 9.5% of engineers contribute almost nothing, costing tech $90B annually, with remote work fueling the rise of "ghost engineers."
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.