search

nexxai / CryptoBlocker

A script to deploy File Server Resource Manager and associated scripts to block infected users
GNU General Public License v2.0
200 stars 73 forks source link

Option to add in second API source #52

Open scholtefrl opened 6 years ago

scholtefrl commented 6 years ago

Is there somehow an option to add in an second api source ? This would be nice since we can then host our own api list besides your api list. This way we can block faster and more specific file extensions.

I already tried to edit an version of the script witch calls upon an diffrent API and ads an diffrent filegroup to the default file template. The problem is somehow the last active script running is the active file group. So when we run our version of the script, our file group is active in the default template. When we run your version of the script your file groups are active in the template. If you could help me resolve this issue then a second api source would not be needed.

StarDestroyer78 commented 6 years ago

If you just want to have a private list that you want to have added to the list provided by Experiant, look into the IncludeList.txt feature (described very briefly in the README). You can use various methods for keeping your IncludeList.txt file up to date.

andi-blafasl commented 5 years ago

I'm using an fork of this repo for my internal usage. It contains a branch which is customized and cloned to all my servers. For updates I fetch the repo from nexxai, merge it into my forked repo and into the branch for my servers. Finally pull this branch to the servers and everything is good to go. With this type of workflow I can track my customization and keep the script up to date from this repo.