shaytan/Pritunl-API-crack
1
0
Fork 0
mirror of https://github.com/Encryptshell/Pritunl-API-crack.git synced 2025-11-29 00:23:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixed typo in README.MD

Browse Source 
Signed-off-by: Simon Beginn <simon@simonmicro.de>
This commit is contained in:
fledermaus101
2021-12-27 21:27:46 +01:00
committed by Simon Beginn
parent 281477a65e
commit 0e7ab6900b
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -2,7 +2,7 @@
This neat script provides a little fake API to unlock all premium/enterprise/enterprise+ (here called ultimate) features of your own Pritunl VPN server. If Pritunl wouldn't be mostly free already, you could call this a crack. An Open Source crack. This neat script provides a little fake API to unlock all premium/enterprise/enterprise+ (here called ultimate) features of your own Pritunl VPN server. If Pritunl wouldn't be mostly free already, you could call this a crack. An Open Source crack.
## How to setup (server) ## ## How to setup (server) ##
Take a look into the `server` folder: You _could_ use the Pritunl source there (or just download this specific version from their GitHub repo) to compile a guaranteed compartible version for this API or just download any other version of the Pritunl server and try your luck. Take a look into the `server` folder: You _could_ use the Pritunl source there (or just download this specific version from their GitHub repo) to compile a guaranteed compatible version for this API or just download any other version of the Pritunl server and try your luck.
Then you'll need to execute the `setup.sh` script (preferable as `root`, as it needs to modify the Pritunl files directly). Then you'll need to execute the `setup.sh` script (preferable as `root`, as it needs to modify the Pritunl files directly).
After that log in into the dashboard - there should be a "Update Notification": After that log in into the dashboard - there should be a "Update Notification":