Notice to ALL Server Owners
This should be paid attention to by ALL people who own a server and run Gmodstore scripts on it:
There has been an excessive amount of reports lately in regards to people claiming their addons may have been compromised due to mishandling or a rogue ex-staff member. We've had a few bans that have come from this -- simply because YOUR user_id was found in the leaked addon. So let's be clear about a few things:
Your server is YOUR RESPONSIBILITY. If you own a server, it is your responsibility to ensure all files are secure. If you have addons that you've purchased on that server, LIMIT access based on the job or when a project requires access to a particular addon.
Don't give total access Stop over-trusting, and giving your co-owners access to every single file. As stated in point one, restrict access until it is NEEDED. Give each person working on your server their own unique FTP credentials. Or better yet, don't allow THAT many people into your server. It's too many chefs in the kitchen.
Keep Logs If you end up being placed in a situation where you have been banned because a rogue staff member leaked your stuff -- WE WANT LOGS. FTP servers have log systems, and this is also why you should give each staff member their OWN credentials. If you are banned, we will ask for proof, if you don't have the proof -- there's a slim chance you'll win your appeal. It's not because we're assholes, it's because we go based on proof. LOG EVERYTHING.
Don't Share The scripts you purchase are YOURS. It's against the terms to give the scripts to others anyway. If you need a purchased script installed, then do it yourself. If you own a server, you should probably be figuring out how to do all of this on your own anyway. If you get stuck on an installation, submit a ticket to the developer of the script. But STOP giving them out to people. You WILL be banned.
We're not trying to be assholes about this, we're trying to get server owners to exercise caution, and be smart. We aren't here to just ban you, BUT we have to keep the developer's work protected as well, and that means eliminating the possibility of a leaker at any and all costs. It's uncalled for that an innocent person must be banned because an ex-staff member decided to screw you over, and you lose all your scripts. But you have to understand our situation -- how do we know you're telling the truth?
Avoid a problem before there is one.
Edit: A new guide has been created: Purchasing Scripts - Guidelines and Tips
Regards, Richard
Should be stickied and a notification to this on the main page... Otherwise the people this is aimed at are never going to read this.
I can confirm this. VCMod detected 8 leaks within the past week alone. Usual rate is around 2-3 per week. Currently dealing with 4 of them who all claim: "my friend stole it" or "I was hacked by that scripthook thing", nice to have somewhere to link them to.
Avoid a problem before their is one.
*there
... I'm a dick
ByRichardat 2nd of May 2017 00:09:26
This should be paid attention to by ALL people who own a server and run Gmodstore scripts on it:There has been an excessive amount of reports lately in regards to people claiming their addons may have been compromised due to mishandling or a rogue ex-staff member. We've had a few bans that have come from this -- simply because YOUR user_id was found in the leaked addon. So let's be clear about a few things:Your server is YOUR RESPONSIBILITY.If you own a server, it is your responsibility to ensure all files are secure. If you have addons that you've purchased on that server, LIMIT access based on the job or when a project requires access to a particular addon.Don't give total accessStop over-trusting, and giving your co-owners access to every single file. As stated in point one, restrict access until it is NEEDED. Give each person working on your server their own unique FTP credentials. Or better yet, don't allow THAT many people into your server. It's too many chefs in the kitchen.Keep LogsIf you end up being placed in a situation where you have been banned because a rogue staff member leaked your stuff -- WE WANT LOGS. FTP servers have log systems, and this is also why you should give each staff member their OWN credentials. If you are banned, we will ask for proof, if you don't have the proof -- there's a slim chance you'll win your appeal. It's not because we're assholes, it's because we go based on proof. LOG EVERYTHING.Don't ShareThe scripts you purchase are YOURS. It's against the terms to give the scripts to others anyway. If you need a purchased script installed, then do it yourself. If you own a server, you should probably be figuring out how to do all of this on your own anyway. If you get stuck on an installation, submit a ticket to the developer of the script. But STOP giving them out to people. You WILL be banned.We're not trying to be assholes about this, we're trying to get server owners to exercise caution, and be smart. We aren't here to just ban you, BUT we have to keep the developer's work protected as well, and that means eliminating the possibility of a leaker at any and all costs. It's uncalled for that an innocent person must be banned because an ex-staff member decided to screw you over, and you lose all your scripts. But you have to understand our situation -- how do we know you're telling the truth?Avoid a problem before their is one.Regards,Richard
Hi ! I totally agree these sentences. Now, with CPanel you can easily add restrictions to your FTP users !
https://documentation.cpanel.net/display/ALD/FTP+Accounts
And for command line :
( There is a lot of f*cking tutorials on the web ) http://www.sherweb.com/blog/how-to-set-up-ftp-access-for-multiple-users-with-user-isolation/ https://docs.oracle.com/cd/E23823_01/html/816-4555/wuftp-43.html
It wasn't really hard to find it, go here to learn how to find something on Google
-snip-
I moved this to the official announcements section as requested.
And thats why you shouldn't have a dev. I mean unless you know him irl. I wouldn't trust anyone with FTP.
There's nothing wrong with having another dev, however. I have my devs work on shit on a local server, then send to me when it's ready for production. It just has to be managed properly.
As long as they're not DarkRP developers, you're fine with having a dev.
Check if your hired developer can actually code™
also check for suitable reputation, not just looking at how many +1's they have but actually reading what the fucking reps say, cause some cunts think this is CoD and boost rep.
This is why in the license it says Licensor hereby grants Licensee a Personal, Non-assignable & non-transferable, , we know you're going to let people of your staff access it, it's just a reason for us to punish someone.
It's easy to say "blahblah, it's him, not me".
Wait so you're saying that I shouldn't give someone FTP? So If I did and if they did leak it without my permission I would get banned.
ByMyNameIsNedat 3rd of May 2017 15:07:57
Wait so you're saying that I shouldn't give someone FTP? So If I did and if they did leak it without my permission I would get banned.
Jup
ByMyNameIsNedat 3rd of May 2017 15:07:57
Wait so you're saying that I shouldn't give someone FTP? So If I did and if they did leak it without my permission I would get banned.
Common sense.
ByMyNameIsNedat 3rd of May 2017 15:07:57
Wait so you're saying that I shouldn't give someone FTP? So If I did and if they did leak it without my permission I would get banned.
Yes. You're responsible.
because YOUR user_id was found in the leaked addon What if someone put YOUR steam_id / user_id into addon and publish it on some leaks site?
By#РосКомМаксимat 8th of May 2017 10:23:36
because YOUR user_id was found in the leaked addonWhat if someone put YOUR steam_id / user_id into addon and publish it on some leaks site?Its not as simple as copy pasting your public steam ID. Once you download a copy your ID is encrypted with private keys and only then added into the code.
Byfreemmaannat 8th of May 2017 10:59:22
Its not as simple as copy pasting your public steam ID. Once you download a copy your ID is encrypted with private keys and only then added into the code.
but if a dumb author puts their userid in the shared files or console prints then it's straight forward right?
Bydrizzy.vip - crident.comat 11th of May 2017 10:00:53
but if a dumb author puts their userid in the shared files or console prints then it's straight forward right?
Pretty obvious of what will happen next. Individual buyers are not to blame for having their copies leaked, in such case.