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
413d301086
sp-hydra-veil-core
/
core
/
services
/
networking
History
SimplifiedPrivacy
71e7dc5cb1
Cross-protocol Firewall kill made easier to access
2026-11-05 18:17:37 -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
Cross-protocol Firewall kill made easier to access
2026-11-05 18:17:37 -05:00
httpx
legacy
mtu
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
Creation of Profile objects now happens in core, instead of GUI
2026-11-05 11:19:40 -05:00
systemwide
Creation of Profile objects now happens in core, instead of GUI
2026-11-05 11:19: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