You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 12, 2021. It is now read-only.
Having the ability to run/enable torghost as a systemd service would significantly improve torghost as an opsec tool. This would mean we can have tor connectivity from system init (boot) and check its status at any time.
Outcome would allow the following systemd commands:
systemctl start torghost -> equivalent to torghost -s systemctl stop torghost -> equivalent to torghost -x systemctl enable torghost -> equivalent to running torghost -s at system init (boot) systemctl status torghost -> standard service status
I'm happy to work this if this is something you're interested in adding to the project @SusmithKrishnan. I could probably have something working in the next few weeks.
This is an expansion on issue #66 (which I would argue is an incomplete workaround).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Having the ability to run/enable torghost as a systemd service would significantly improve torghost as an opsec tool. This would mean we can have tor connectivity from system init (boot) and check its status at any time.
Outcome would allow the following systemd commands:
systemctl start torghost
-> equivalent totorghost -s
systemctl stop torghost
-> equivalent totorghost -x
systemctl enable torghost
-> equivalent to runningtorghost -s
at system init (boot)systemctl status torghost
-> standard service statusI'm happy to work this if this is something you're interested in adding to the project @SusmithKrishnan. I could probably have something working in the next few weeks.
This is an expansion on issue #66 (which I would argue is an incomplete workaround).
The text was updated successfully, but these errors were encountered: