Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable Tor relay node #82

Open
4 tasks
MattDHill opened this issue Dec 3, 2020 · 3 comments
Open
4 tasks

Enable Tor relay node #82

MattDHill opened this issue Dec 3, 2020 · 3 comments
Assignees
Labels
Enhancement New feature or request Needs Scoping Requirements are not fully defined P3 - Eventual Things of low consequence to ignore startd Issues pertaining to startd itself UI Issues pertaining to any of the embassy-served web applications

Comments

@MattDHill
Copy link
Member

MattDHill commented Dec 3, 2020

  • User should be able to toggle this on/off. Defaults to off.
  • Edit torrc from embassyd
  • Write guide/instructions for setting up port forwarding on router
  • Explain benefits and limitations of enabling this feature

NOT IN SCOPE

  • Automatic setting up of uPnP or port forwarding
@MattDHill MattDHill added UI Issues pertaining to any of the embassy-served web applications Agent labels Dec 3, 2020
@MattDHill MattDHill removed the Agent label Sep 2, 2021
@MattDHill MattDHill changed the title Enable Tor relay node functionality Enable Tor relay node Sep 2, 2021
@MattDHill MattDHill added the startd Issues pertaining to startd itself label Sep 2, 2021
@ProofOfKeags ProofOfKeags added P3 - Eventual Things of low consequence to ignore Needs Scoping Requirements are not fully defined Enhancement New feature or request labels Sep 22, 2021
@ProofOfKeags ProofOfKeags added P1 - Blocks Release This issue must be addressed before the coming release is shipped and removed P3 - Eventual Things of low consequence to ignore labels Oct 28, 2021
@ProofOfKeags ProofOfKeags added this to the 0.3.1 milestone Oct 28, 2021
@24309
Copy link

24309 commented Dec 9, 2021

Hy embassy team, some additional comments

  • User should be able to choose to run a Tor exit or non-exit (bridge/guard/middle) relay
  • User should be able to control the bandwidth that he wants to allow for Tor traffic
  • When the user selects an exit node, the user should to and know how to respond to abuse messages (usualy within 24h)
  • For an exit node, the ip address that is visible to the outside world should have a active web page that describes that he is a Tor exit node
  • On a exit node user should be able to decide whitch Tor traffic he wants to pass through - port restrictions
  • On a exit node, user shoud be alble to set an email address for ContactInfo, that is made public
  • On a exit node user should know the relevant legal paragraphs for common-carrier like communication services in his country like Netherlands: Artikel 6:196c BW / Germany: TMG 8 and 15. / Austria: ECG 13 / USA: DMCA 512
  • On a exit node user should be aware of abuse templates https://www.torservers.net/wiki/abuse/templates

@chrisguida
Copy link
Contributor

Exit nodes are out of scope for now I think.

@ProofOfKeags ProofOfKeags added P3 - Eventual Things of low consequence to ignore and removed P1 - Blocks Release This issue must be addressed before the coming release is shipped labels Mar 10, 2022
@ProofOfKeags ProofOfKeags removed this from the 0.3.1 milestone Mar 10, 2022
@MattDHill
Copy link
Member Author

Plan is to convert Tor into a package with system implications. Add-ons/plugins story

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request Needs Scoping Requirements are not fully defined P3 - Eventual Things of low consequence to ignore startd Issues pertaining to startd itself UI Issues pertaining to any of the embassy-served web applications
Projects
None yet
Development

No branches or pull requests

5 participants