Skip to content

purplemaze-net/Agent

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

20 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

PurpleMaze Agent (Pagent)

Introduction

As I own PurpleMaze, an Anti-DDoS solution with rotating proxies, it became clear to me that I needed to find a way of authorizing only the IPs currently in use on customers' servers to prevent them from being scanned. So I developed this Pagent with this in mind.

Why open source?

as the software will be installed on the customer's server, I want to be as transparent as possible about its use. The Pagent is compiled for each client with a different SensitiveVars.cs, depending on the client. The other files remain unchanged.

How does it work?

On startup, the Pagent retrieves the list of IPs from the Master server and adds them to the whitelist of necessary ports, then closes these ports to the rest of the Internet.
PurpleMaze's core servers make a request to the Pagent as soon as a proxy is created or deleted for the server, to add or remove its IP from the whitelist.

How to build ?

Well, even if I don't know why you would want to build it yourself, you can do it by:

  • Clone the repo
  • Rename src/SensitiveVars.example.cs to src/SensitiveVars.cs and fill it with your own values
  • Install DotNet SDK 6.0+
  • Run the "build.bat" file (Both Windows and Linux are supported)
  • Solutions in bin/Release/net6.0/linux-x64/publish and bin/Release/net6.0/win-x64/publish

Can I help ?

Of course! Don't hesitate to make a PR or contact me on Discord (@m2p_) if you see a possible improvement.

Post-Scriptum

This software was not originally developed with open-source in mind, which explains the lack of commentary and some breaches of standards.

About

IP Whitelists made simple.

Resources

License

Stars

Watchers

Forks

Languages

  • C# 99.1%
  • Batchfile 0.9%