IMPLEMENTATION PATH

asandikci commented

2023-08-19 16:23:47 +03:00

Owner

--- DEVELOPMENT PHASE ---

Buy first server
Fork all strongswan server/apps
Create your own docker for strongswan
Deploy docker to your server
- Create a scripts for auto handling creating/configuring servers/dockers/connections (for providing easy setup to other servers)
Learn how to Manage Statistics for servers/users
Prepare a basic web interface (basic things in #2)
- index.php, setup/, usage/
- Mailing support (initialize first password with mail)
- basic user/ (just password change)
Store User data in plain text-password in each server (1 server currently)
- alsavnp-server1.xyx -> user-a : pass123 (builtin strongswan functionality)

--- ALPHA PHASE | 30 September ---

Ready to use for a small group (~10 IFL student, 1 server)

Implement Hash Support for both server and clients (#1)
Prepare a proper web interface (all in #2)
Add links (github, wiki, blog, social) to client apps
Semi-Auto Signup with mailing (users send request via IM to admin, admin approve and send a registration link manually(seperate server link, xxx.xxx.xxx.xxx/register?hash=A-RANDOM-SERVER-VALIDATED-HASH-HERE?payment=done?username-placeholder=user1). Then user signups with mail/username/pass, mail verification and lastly sees /user/ page)
- Inform users that https is not implemented and use a different password with other passwords
Android app for quick admin processes (like adding temporary keys to server for validating a user has been paid as cash a subscription,generating a link for a dedicated server for a user signup(see link above), seeing stats of servers/users, locking all servers for maintenance, restart all servers, open/close verbose logging, listing all servers and user information...)
Admin Subscription management. Monthly payment tracker, auto user payment mail, auto user remove after 5 days or readd if payment done again...

--- BETA PHASE | 15 November ---

More functionality and ready to use for a bigger group (~40 IFL student, 2-3 server). Repositories will be open source with this phase! (+github mirror)

Remove only password (hashless) support for both clients and servers
Built-in payment page (do not stores card info!)
Auto signup with mail/username/pass (using a main server, see below)
Implement communication between vpn servers. At the end of the day we can choose vpn server and use that server without storing our password/hash in this server like Proton (Main Server Based Authentication or sync user-hash across servers?)
Manage user statistics
Limiting machine number in a server
Limiting machine number for a user
Suspicious login/register/usage report
- Report if an user registers without payment or a payment code
- Report if an user connects to a server too frequently
- Report if an user uses more than 10 GiB of network data in a day

--- PUBLIC PHASE | 2024 ---

Ready to use publicly (~100IFL student, 10 server), make Extra Feature Implementations after this phase

Look for similar services and add functionality to both server and client apps
Add another protocol
Make improvements for IPv6
AdGuard/PiHole supported Servers with enhanced security
Special servers for users
Better payment implementations

--- Active Development Until 2025 ---

### --- DEVELOPMENT PHASE --- - [ ] Buy first server - [x] Fork all strongswan server/apps - [ ] Create your own docker for strongswan - [ ] Deploy docker to your server - [ ] Create a scripts for auto handling creating/configuring servers/dockers/connections (for providing easy setup to other servers) - [ ] Learn how to Manage Statistics for servers/users - [ ] Prepare a basic web interface (basic things in #2) - [x] index.php, setup/, usage/ - [ ] Mailing support (initialize first password with mail) - [ ] basic user/ (just password change) - [ ] Store User data in plain text-password in each server (1 server currently) - [ ] alsavnp-server1.xyx -> user-a : pass123 (builtin strongswan functionality) ### --- ALPHA PHASE | 30 September --- > Ready to use for a small group (~10 IFL student, 1 server) --- - [ ] Implement Hash Support for both server and clients (#1) - [ ] Prepare a proper web interface (all in #2) - [ ] Add links (github, wiki, blog, social) to client apps - [ ] Semi-Auto Signup with mailing (users send request via IM to admin, admin approve and send a registration link manually(seperate server link, `xxx.xxx.xxx.xxx/register?hash=A-RANDOM-SERVER-VALIDATED-HASH-HERE?payment=done?username-placeholder=user1`). Then user signups with mail/username/pass, mail verification and lastly sees /user/ page) - [ ] Inform users that https is not implemented and use a different password with other passwords - [ ] Android app for quick admin processes (like adding temporary keys to server for validating a user has been paid as cash a subscription,generating a link for a dedicated server for a user signup(see link above), seeing stats of servers/users, locking all servers for maintenance, restart all servers, open/close verbose logging, listing all servers and user information...) - [ ] Admin Subscription management. Monthly payment tracker, auto user payment mail, auto user remove after 5 days or readd if payment done again... ### --- BETA PHASE | 15 November --- > More functionality and ready to use for a bigger group (~40 IFL student, 2-3 server). Repositories will be open source with this phase! (+github mirror) --- - [ ] Remove only password (hashless) support for both clients and servers - [ ] Built-in payment page (do not stores card info!) - [ ] Auto signup with mail/username/pass (using a main server, see below) - [ ] Implement communication between vpn servers. At the end of the day we can choose vpn server and use that server without storing our password/hash in this server like **Proton** (Main Server Based Authentication or sync user-hash across servers?) - [ ] Manage user statistics - [ ] Limiting machine number in a server - [ ] Limiting machine number for a user - [ ] Suspicious login/register/usage report - [ ] Report if an user registers without payment or a payment code - [ ] Report if an user connects to a server too frequently - [ ] Report if an user uses more than 10 GiB of network data in a day ### --- PUBLIC PHASE | 2024 --- > Ready to use publicly (~100IFL student, 10 server), make Extra Feature Implementations after this phase --- - [ ] Look for similar services and add functionality to both server and client apps - [ ] Add another protocol - [ ] Make improvements for IPv6 - [ ] AdGuard/PiHole supported Servers with enhanced security - [ ] Special servers for users - [ ] Better payment implementations ### --- Active Development Until 2025 ---