This website requires JavaScript.
Explore
Help
Sign In
Support
/
sp-hydra-veil-core
Watch
2
Star
0
Fork
You've already forked sp-hydra-veil-core
0
Code
Issues
Pull requests
1
Projects
Releases
Packages
Wiki
Activity
Actions
4096196849
sp-hydra-veil-core
/
core
/
services
/
networking
History
SimplifiedPrivacy
b073ce2fa5
tweak, increase timeout for async
2026-11-02 14:57:58 -05:00
..
api_requests
Tor profile cleanup and error handling. Moved more functions out of ConnectionController
2026-11-01 17:42:48 -05:00
general_connection_tools
tweak, increase timeout for async
2026-11-02 14:57:58 -05:00
httpx
Introduced Location & MTU testing on systemwide Wireguard. As well as IP address testing instead of the previous method. Additionally, 400 status APIs now pass through the APIResponse layer as True to be evaluated by the SeverReply Layer. Finally notifications are better integrated to convey the testing rounds to the end user.
2026-10-21 13:37:21 -04:00
legacy
mtu
Plumbing and wireguard loop fixed, via using the controller only to modify systemstate, and fixing a bug in the plumbing for the 'no option' functions being run without execute
2026-10-27 17:05:20 -04:00
ports
Introduced an Error Checking loop for Session networking, similar to what is already implemented in Systemwide, with the same ConnectionRecovery dataclass module. But most of these steps/functions have been moved from being in systemwide wireguard itself, to isolated modules (that session's network loop now calls upon). The reason for this change, is so that in a future transition, systemwide can refactor to re-using them also. On a different note, for ip checking, now asyncio is used for session profiles with a proxy port. While threading and multi-process que is used for systemwide profiles.
2026-11-02 14:27:40 -05:00
session
Introduced an Error Checking loop for Session networking, similar to what is already implemented in Systemwide, with the same ConnectionRecovery dataclass module. But most of these steps/functions have been moved from being in systemwide wireguard itself, to isolated modules (that session's network loop now calls upon). The reason for this change, is so that in a future transition, systemwide can refactor to re-using them also. On a different note, for ip checking, now asyncio is used for session profiles with a proxy port. While threading and multi-process que is used for systemwide profiles.
2026-11-02 14:27:40 -05:00
systemwide
Introduced an Error Checking loop for Session networking, similar to what is already implemented in Systemwide, with the same ConnectionRecovery dataclass module. But most of these steps/functions have been moved from being in systemwide wireguard itself, to isolated modules (that session's network loop now calls upon). The reason for this change, is so that in a future transition, systemwide can refactor to re-using them also. On a different note, for ip checking, now asyncio is used for session profiles with a proxy port. While threading and multi-process que is used for systemwide profiles.
2026-11-02 14:27:40 -05:00
tor_tools
Tor profile cleanup and error handling. Moved more functions out of ConnectionController
2026-11-01 17:42:48 -05:00
wireguard
Introduced an Error Checking loop for Session networking, similar to what is already implemented in Systemwide, with the same ConnectionRecovery dataclass module. But most of these steps/functions have been moved from being in systemwide wireguard itself, to isolated modules (that session's network loop now calls upon). The reason for this change, is so that in a future transition, systemwide can refactor to re-using them also. On a different note, for ip checking, now asyncio is used for session profiles with a proxy port. While threading and multi-process que is used for systemwide profiles.
2026-11-02 14:27:40 -05:00
make_url.py