Disroot as tor hidden service #369

Open
opened 2022-11-13 16:03:21 +01:00 by emdee · 19 comments

People have been asking for Disroot as tor hidden service for 5 years now. Privacy is getting more and more important, and some contries are blocking the outside clearnet completely.

It will run fine out of the box on any linux, and it's only 3 lines of extra configuration to the /etc/torrc Run:

tor --hash-password something secret

and plug the long value into the next line:

HashedControlPassword 16:...
ControlSocket /run/tor/control GroupWritable RelaxDirModeCheck
ExitPolicy reject *:*

The control socket is so you can run diagnostic tools like nyx and it's rw tor user only.

Plus 2 lines for each service you want onioned (all please :-)


# Mumble hidden service configuration.
HiddenServiceDir /var/lib/tor/mumble-hsv3/
HiddenServicePort 64738 127.0.0.1:64738

Then look in each of the /var/lib/tor/*-hsv3/hostname
to get the onion addresses of each of the services you run and put them up in your web pages.

If you have a firewall, you need to open it for the user tor is running as, TCP ports only. You can even restrict it to ports 443,8000-9999 and safely cover most of the traffic.

@muppeth Can't take more than an hour all tolled; about 12 minutes for each year it's been asked for :-)

This was one of the first issues raised 2 years ago #29

People have been asking for Disroot as tor hidden service for 5 years now. Privacy is getting more and more important, and some contries are blocking the outside clearnet completely. It will run fine out of the box on any linux, and it's only 3 lines of extra configuration to the ```/etc/torrc``` Run: ``` tor --hash-password something secret ``` and plug the long value into the next line: ``` HashedControlPassword 16:... ControlSocket /run/tor/control GroupWritable RelaxDirModeCheck ExitPolicy reject *:* ``` The control socket is so you can run diagnostic tools like ```nyx``` and it's rw tor user only. Plus 2 lines for each service you want onioned (all please :-) ``` # Mumble hidden service configuration. HiddenServiceDir /var/lib/tor/mumble-hsv3/ HiddenServicePort 64738 127.0.0.1:64738 ``` Then look in each of the ```/var/lib/tor/*-hsv3/hostname``` to get the onion addresses of each of the services you run and put them up in your web pages. If you have a firewall, you need to open it for the user tor is running as, TCP ports only. You can even restrict it to ports 443,8000-9999 and safely cover most of the traffic. @muppeth Can't take more than an hour all tolled; about 12 minutes for each year it's been asked for :-) * https://forum.disroot.org/t/any-plans-on-making-an-onion-domain/8557 * https://forum.disroot.org/t/disroot-as-tor-hidden-service/1971 This was one of the first issues raised 2 years ago https://git.disroot.org/Disroot/Disroot-Project/issues/29
meaz added this to the 11.22 - November milestone 2022-12-02 18:20:58 +01:00
meaz modified the milestone from 11.22 - November to 12.22 - December 2022-12-02 18:21:00 +01:00
meaz was assigned by muppeth 2022-12-07 21:12:47 +01:00
muppeth added the
duplicate
label 2022-12-07 21:12:53 +01:00
muppeth added this to the 12.22 - December project 2022-12-08 23:29:16 +01:00
Owner

Are are almost ready to push this. I still need to check and possibly update current setup on proxy servers and once this is cleared up, push it.

Are are almost ready to push this. I still need to check and possibly update current setup on proxy servers and once this is cleared up, push it.
muppeth removed the
duplicate
label 2022-12-24 10:06:09 +01:00
Owner

We will deployed normally during next deployment frame: Disroot/CHANGELOG#361

We will deployed normally during next deployment frame: https://git.disroot.org/Disroot/CHANGELOG/issues/361
meaz closed this issue 2023-01-04 22:01:32 +01:00
Author

@meaz Has this been pushed yet? I see no mention of it on the homepage.

What services are supported? It's easy to support mutiple ports on one tor instance.

@muppeth People have been asking for Disroot as tor hidden service for 6 years now. It's not more than a hour's work to set all of this up...

@meaz Has this been pushed yet? I see no mention of it on the homepage. What services are supported? It's easy to support mutiple ports on one tor instance. @muppeth People have been asking for Disroot as tor hidden service for 6 years now. It's not more than a hour's work to set all of this up...
Author

Repoening as I am the originator and it has not been resolved in my view.

Repoening as I am the originator and it has not been resolved in my view.
emdee reopened this issue 2023-07-14 18:02:38 +02:00
Owner

@emdee This has been rolled out as mentioned.

We arent providing mail (SMTP/IMAP) nor xmpp (5222) as we still need to assess possible abuse.

@emdee This has been rolled out as mentioned. - Set of services are available as onion address since March as posted in https://disroot.org/en/blog/disnews-9 - The info whether the onion address is provided is on each service page eg:https://disroot.org/en/services/email - Additionally we provide `add_header Onion-Location` on *"plain"* address so people can easily switch to onion one. We arent providing mail (SMTP/IMAP) nor xmpp (5222) as we still need to assess possible abuse.
Author

Nice to know that things might be progressing every few years (@muppeth :-), but:

  1. There is no listing of the onion address on the homepage where it should be.

  2. There is no listing of the onion addresses on the disnews-9 post where it might be.

  3. There is no listing of the onion addresses on the service page where I hoped it would be https://disroot.org/en/services/email

  4. There is no autodetection in the browser for disroot.org

  5. If the onion address is the one autodetected in the browser on git.disroot.org
    http://kgtz2pmmov5jfvn3z4mqryffjnnw6krzrgxxoyaqhqckjrr4pckyhsqd.onion/

then it's not working:

502 Bad Gateway
nginx

  1. What are the domains that are autodetecting and which are not?

  2. If you will be onioning the webmail then you need to explain why you are not onioning SMTP/POP3/IMAP - instead of a blog post on a blog most people don't know about, how about a webpage on Tor access linked to from the homepage, and linked to from each supported service page? It should list the services you are planning to support, and the decade/century in which the onion service is planned for. Some of them can be done now: e.g. mumble.

  3. Are there are any tests for this? If so they are not working. (If it's not tested it's broken :-()

Reopening as I am the originator and it has not been resolved in my view; this is why it's considered more professional to get the originator to close an issue, so that they confirm the issue has been addressed and solved.

Nice to know that things might be progressing every few years (@muppeth :-), but: 1) There is no listing of the onion address on the homepage where it should be. 2) There is no listing of the onion addresses on the disnews-9 post where it might be. 3) There is no listing of the onion addresses on the service page where I hoped it would be https://disroot.org/en/services/email 4) There is no autodetection in the browser for disroot.org 5) If the onion address is the one autodetected in the browser on git.disroot.org http://kgtz2pmmov5jfvn3z4mqryffjnnw6krzrgxxoyaqhqckjrr4pckyhsqd.onion/ then it's not working: 502 Bad Gateway nginx 6) What are the domains that are autodetecting and which are not? 7) If you will be onioning the webmail then you need to explain why you are not onioning SMTP/POP3/IMAP - instead of a blog post on a blog most people don't know about, how about a webpage on Tor access linked to from the homepage, and linked to from each supported service page? It should list the services you are planning to support, and the decade/century in which the onion service is planned for. Some of them can be done now: e.g. mumble. 8) Are there are any tests for this? If so they are not working. (If it's not tested it's broken :-() Reopening as I am the originator and it has not been resolved in my view; this is why it's considered more professional to get the originator to close an issue, so that they confirm the issue has been addressed and solved.
emdee reopened this issue 2023-07-21 15:51:16 +02:00
Owner

Hi there,
Thanks for being presistant with your issue. Below some explanations and additional issues created that should speed up things and hopefully you won't need to wait until humanity builds a Dyson sphere to get onion services for the entire platform.

There is no listing of the onion address on the homepage where it should be.

That's because it's listed on service page. Adding onion button for each tile of the service on the front page would just add clutter and we decided not to do it because:

  • Link is on the service page
  • Onion addresses are (should) be autodetected.

There is no listing of the onion addresses on the disnews-9 post where it might be.

Because those are posted on the service page and are autodetected. If they aren't means they are missing link for one or another reason.

There is no listing of the onion addresses on the service page where I hoped it would be

Simply untrue. Go again to the page you linked (email), Next to "signup" and "Login" you have "Tor" button. That applies to every service with existing onion address.

There is no autodetection in the browser for disroot.org

Sould be, but looks like the header is not recognized by the browser. That vhost serving is a particular one with few other locations so this could be the reason. I made an issue to fix it: #564

If the onion address is the one autodetected in the browser on git.disroot.org'

Fixed! There was a little issue with the proxy server after migration that wasn't pointing to proper destination for the onion vhost. Thanks for reporting. I fixed it in production and supplied a fix to orchestration for permanent fix.

What are the domains that are autodetecting and which are not?

Info provided on page of each service.

If you will be onioning the webmail then you need to explain why you are not onioning SMTP/POP3/IMAP - instead of a blog post on a blog most people don't know about, how about a webpage on Tor access linked to from the homepage, and linked to from each supported service page? It should list the services you are planning to support, and the decade/century in which the onion service is planned for. Some of them can be done now: e.g. mumble.

Don't see reason why should we explain on seperate page things like why we provide A but not B. Main goal is to provide all services but main condition is possible abuse. So some services are easier and are or will be (look below) provided, and some need some extra thought put to it.
I think it's quite obvious why we dont provide imap/pop3/smtp over tor. We need to asses and prepare servers and ourself for possible counter actions against abuse. Today you complain there is no imap support for tor, tomorrow you will complain everyone is blocking disroot domains. At this moment we have other priorities and so there is no ETA on when will that happen, but given there are people like yourself looking forward to it, adds some extra priority points. Whether it will be done this century or not, is not known yet. Ping me next decade if it didnt happen yet? :)

  • For email for better tracking I made: #566
  • For xmpp: #567
  • As for mumble. Sure we could add it. #565

I will add all issues I just made as dependency for this issue so you can follow it. I hope the explanations given are clear even if not exactly what you would like. If you have suggestions comments, ideas, please feel free to post. As pointed out indeed I think I have rushed with closing this ticket. Specially without creating the followup issues. That would definitely push the whole process beyond reaching singularity or even further.

Hi there, Thanks for being presistant with your issue. Below some explanations and additional issues created that should speed up things and hopefully you won't need to wait until humanity builds a Dyson sphere to get onion services for the entire platform. > There is no listing of the onion address on the homepage where it should be. That's because it's listed on service page. Adding onion button for each tile of the service on the front page would just add clutter and we decided not to do it because: - Link is on the service page - Onion addresses are (should) be autodetected. > There is no listing of the onion addresses on the disnews-9 post where it might be. Because those are posted on the service page and are autodetected. If they aren't means they are missing link for one or another reason. > There is no listing of the onion addresses on the service page where I hoped it would be Simply untrue. Go again to the page you linked (email), Next to "signup" and "Login" you have "Tor" button. That applies to every service with existing onion address. > There is no autodetection in the browser for disroot.org Sould be, but looks like the header is not recognized by the browser. That vhost serving is a particular one with few other locations so this could be the reason. I made an issue to fix it: #564 > If the onion address is the one autodetected in the browser on git.disroot.org' Fixed! There was a little issue with the proxy server after migration that wasn't pointing to proper destination for the onion vhost. Thanks for reporting. I fixed it in production and supplied a fix to orchestration for permanent fix. > What are the domains that are autodetecting and which are not? Info provided on page of each service. > If you will be onioning the webmail then you need to explain why you are not onioning SMTP/POP3/IMAP - instead of a blog post on a blog most people don't know about, how about a webpage on Tor access linked to from the homepage, and linked to from each supported service page? It should list the services you are planning to support, and the decade/century in which the onion service is planned for. Some of them can be done now: e.g. mumble. Don't see reason why should we explain on seperate page things like why we provide A but not B. Main goal is to provide all services but main condition is possible abuse. So some services are easier and are or will be (look below) provided, and some need some extra thought put to it. I think it's quite obvious why we dont provide imap/pop3/smtp over tor. We need to asses and prepare servers and ourself for possible counter actions against abuse. Today you complain there is no imap support for tor, tomorrow you will complain everyone is blocking disroot domains. At this moment we have other priorities and so there is no ETA on when will that happen, but given there are people like yourself looking forward to it, adds some extra priority points. Whether it will be done this century or not, is not known yet. Ping me next decade if it didnt happen yet? :) - For email for better tracking I made: #566 - For xmpp: #567 - As for mumble. Sure we could add it. #565 I will add all issues I just made as dependency for this issue so you can follow it. I hope the explanations given are clear even if not exactly what you would like. If you have suggestions comments, ideas, please feel free to post. As pointed out indeed I think I have rushed with closing this ticket. Specially without creating the followup issues. That would definitely push the whole process beyond reaching singularity or even further.
muppeth added a new dependency 2023-07-22 15:09:00 +02:00
muppeth added a new dependency 2023-07-22 15:09:24 +02:00
muppeth added a new dependency 2023-07-22 15:09:43 +02:00
muppeth added a new dependency 2023-07-22 15:10:00 +02:00
Author

Thanks for your help, and sorry I missed the Tor button; when I look for an onion link, I tend to look for the text "onion" on a page, and to me "explcit is better than implicit". So some suggestions are:

  1. Make the onion link on the Home page explicit.

  2. Make the onion link on the service/email page explicit as well as the button, and note that you still don't support IMAP/POP3/SMTP yet.

  3. Don't rely on the autodetect too much as it may not be a browser that knows autodetect that is accessing the service. Also, autosuggestion is a configurable preference and may be turned off globally in the browser.

Not trying to be ornery, but let me continue with what's still ToDo:

  1. The link pointed to by Tor on services/email doesn't work:
    http://vvobhgocv3jvjwjjyrocao3vij4q7xuk5panbckqwihuztuuvjiwqdid.onion/

  2. There is no mention of Tor on the homepage.

  3. The link autosuggested by disroot.org/en goes somewhere else http://j4dhkkxfcsvzvh3p5djkmuehhgd6t6l7wmzih6b4ss744hegwkiae7ad.onion/ but doesn't it work.

  4. The onion link in 4) is different from the autodetect link I listed above (which now does work) - probably git. vs www.. As there are now multiple different onion addresses it would be nice to have an explanation on the homepage, or better yet, a Tor page that lists all of the Tor services, active now and planned ( and those drooled over). I'm already lost following the different onions, and having them all linked to and summarized in one place will make it easier to test.

  5. The Tor button on /nextcloud points to http://3rhtbo7bb3o5qvx2iyirppxxtpwnlxkavdyjdckmuzh2uohibignufqd.onion/ which redirects automatically to https://cloud.disroot.org/login :-(
    The autodetect points to http://j4dhkkxfcsvzvh3p5djkmuehhgd6t6l7wmzih6b4ss744hegwkiae7ad.onion/en/services/nextcloud which does NOT work, and I think is wrong. Maybe open an issue to add Tor to nextcloud?

  6. The Tor button on /services/search works but the autodetect does NOT - http://j4dhkkxfcsvzvh3p5djkmuehhgd6t6l7wmzih6b4ss744hegwkiae7ad.onion/en/services/search

  7. The Tor button/services/cryptpad works but the autodetect does NOT - http://j4dhkkxfcsvzvh3p5djkmuehhgd6t6l7wmzih6b4ss744hegwkiae7ad.onion/en/services/cryptpad Add an issue for /cryptpad ?

  8. /services/privatebin has a Tor button that does NOT work to http://j4dhkkxfcsvzvh3p5djkmuehhgd6t6l7wmzih6b4ss744hegwkiae7ad.onion/en/services/privatebin NOR does the autodetect at http://fgb4city54qtch7pdulgryete6hora4dmsrbuygoczrcdtlgpudaftid.onion/ Add an issue for /privatebin ?

  9. There are clearly no tests written to make sure the links work. Maybe you could open a separate issue to add the tests to your testsuite and you can make that issue dependent on this one. (If it aint tested, its broke.) Take over #578

Thanks for opening #565 #566 #567 and I suggest keeping this open as a point to coordinate overall, including discussing priority/safety.

IMHO (commented on their pages):
a) xmpp over Tor is widely in use, and most places just turn off anonymous signup over Tor.

b) mumble works over Tor - I can help you test it.

c) I never got jitsi to work over Tor - I doubt it's possible. Tox works for voice and chat.

c) I understand the risk of SMTP and IMAP, but do you agree that POP3 is relatively safe?

d) open an issue to add Tor to Akkoma?

Thanks for a great start:

sed -e 's/century/millenium/g' :-)
sed -e 's/an hour/a week/g' :-(

Thanks for your help, and sorry I missed the Tor button; when I look for an onion link, I tend to look for the text "onion" on a page, and to me "explcit is better than implicit". So some suggestions are: 1) Make the onion link on the Home page explicit. 2) Make the onion link on the service/email page explicit as well as the button, and note that you still don't support IMAP/POP3/SMTP yet. 3) Don't rely on the autodetect too much as it may not be a browser that knows autodetect that is accessing the service. Also, autosuggestion is a configurable preference and may be turned off globally in the browser. Not trying to be ornery, but let me continue with what's still ToDo: 4) The link pointed to by Tor on services/email doesn't work: http://vvobhgocv3jvjwjjyrocao3vij4q7xuk5panbckqwihuztuuvjiwqdid.onion/ 5) There is no mention of Tor on the homepage. 6) The link autosuggested by disroot.org/en goes somewhere else http://j4dhkkxfcsvzvh3p5djkmuehhgd6t6l7wmzih6b4ss744hegwkiae7ad.onion/ but doesn't it work. 7) The onion link in 4) is different from the autodetect link I listed above (which now does work) - probably git. vs www.. As there are now multiple different onion addresses it would be nice to have an explanation on the homepage, or better yet, a Tor page that lists all of the Tor services, active now and planned ( and those drooled over). I'm already lost following the different onions, and having them all linked to and summarized in one place will make it easier to test. 8) The Tor button on /nextcloud points to http://3rhtbo7bb3o5qvx2iyirppxxtpwnlxkavdyjdckmuzh2uohibignufqd.onion/ which redirects automatically to https://cloud.disroot.org/login :-( The autodetect points to http://j4dhkkxfcsvzvh3p5djkmuehhgd6t6l7wmzih6b4ss744hegwkiae7ad.onion/en/services/nextcloud which does NOT work, and I think is wrong. Maybe open an issue to add Tor to nextcloud? 9) The Tor button on /services/search works but the autodetect does NOT - http://j4dhkkxfcsvzvh3p5djkmuehhgd6t6l7wmzih6b4ss744hegwkiae7ad.onion/en/services/search 10) The Tor button/services/cryptpad works but the autodetect does NOT - http://j4dhkkxfcsvzvh3p5djkmuehhgd6t6l7wmzih6b4ss744hegwkiae7ad.onion/en/services/cryptpad Add an issue for /cryptpad ? 11) /services/privatebin has a Tor button that does NOT work to http://j4dhkkxfcsvzvh3p5djkmuehhgd6t6l7wmzih6b4ss744hegwkiae7ad.onion/en/services/privatebin NOR does the autodetect at http://fgb4city54qtch7pdulgryete6hora4dmsrbuygoczrcdtlgpudaftid.onion/ Add an issue for /privatebin ? 12) There are clearly no tests written to make sure the links work. Maybe you could open a separate issue to add the tests to your testsuite and you can make that issue dependent on this one. (If it aint tested, its broke.) Take over https://git.disroot.org/Disroot/Disroot-Project/issues/578 Thanks for opening https://git.disroot.org/Disroot/Disroot-Project/issues/565 https://git.disroot.org/Disroot/Disroot-Project/issues/566 https://git.disroot.org/Disroot/Disroot-Project/issues/567 and I suggest keeping this open as a point to coordinate overall, including discussing priority/safety. IMHO (commented on their pages): a) xmpp over Tor is widely in use, and most places just turn off anonymous signup over Tor. b) mumble works over Tor - I can help you test it. c) I never got jitsi to work over Tor - I doubt it's possible. Tox works for voice and chat. c) I understand the risk of SMTP and IMAP, but do you agree that POP3 is relatively safe? d) open an issue to add Tor to Akkoma? Thanks for a great start: > sed -e 's/century/millenium/g' :-) > sed -e 's/an hour/a week/g' :-(
Owner

Thanks for reply. Just quick reply to some of the things you pointed out. There was changes where we migrated some of the services over to different host and re-generated onion addresses, but didnt update the website (duh...). Made pull request with corrections and it's awaiting approval so once it's clear, it will be updated on the website.

Make the onion link on the Home page explicit.

Yes should make that one as a direct link in the footer. (address is one click too far)

Don't rely on the autodetect too much as it may not be a browser that knows autodetect that is accessing the service. Also, autosuggestion is a configurable preference and may be turned off globally in the browser.

Thats why we are also adding addresses on the pages (as explained above mistake is being fixed)

Tor page that lists all of the Tor services, active now and planned

Since we have such page (link in the footer of the website) perhaps it's not a bad idea to actually add more info to it as you suggested (https://disroot.org/en/tor )
That would mean I rather then not put onion address on the website but keep it as is on that page. As I said it's just one click away and you will also get the list of services and all other needed info in one place. #568

There is no mention of Tor on the homepage.

Check footer. See above

The Tor button on /nextcloud...

Indeed nextcloud overwrites the hostname so will need to check it more in detail and see if we can easily do it. #569

cryptpad

That's also a bit more complex issue then just adding vhost replacing the server name as there are two seperate vhosts for it and may render some issues. #570

akkoma

#571

There are clearly no tests written to make sure the links work.

We normally monitor the service's internals to determine the sate of the service, OS it hosted on, dependant services like php or sql etc. Usually this gives us enough info to know when something's up. For http hosts we additionally monitor by checking http reponse code. Haven't add any for onion addresses assuming if plain works so should onion, though that wasn't the case.

It's true we "rushed" pushing the tor related stuff because it was just embarissing how long it took (I made the initial issue as one of the first ones after we started disroot, so I know damn well how bad it feels). But thanks to your reporting and persistancy (I really enjoy it actually) things will get done right. So thanks for ass kicking and great work!

Thanks for reply. Just quick reply to some of the things you pointed out. There was changes where we migrated some of the services over to different host and re-generated onion addresses, but didnt update the website (duh...). Made pull request with corrections and it's awaiting approval so once it's clear, it will be updated on the website. > Make the onion link on the Home page explicit. Yes should make that one as a direct link in the footer. (address is one click too far) > Don't rely on the autodetect too much as it may not be a browser that knows autodetect that is accessing the service. Also, autosuggestion is a configurable preference and may be turned off globally in the browser. Thats why we are also adding addresses on the pages (as explained above mistake is being fixed) > Tor page that lists all of the Tor services, active now and planned Since we have such page (link in the footer of the website) perhaps it's not a bad idea to actually add more info to it as you suggested (https://disroot.org/en/tor ) That would mean I rather then not put onion address on the website but keep it as is on that page. As I said it's just one click away and you will also get the list of services and all other needed info in one place. #568 > There is no mention of Tor on the homepage. Check footer. See above > The Tor button on /nextcloud... Indeed nextcloud overwrites the hostname so will need to check it more in detail and see if we can easily do it. #569 > cryptpad That's also a bit more complex issue then just adding vhost replacing the server name as there are two seperate vhosts for it and may render some issues. #570 > akkoma #571 > There are clearly no tests written to make sure the links work. We normally monitor the service's internals to determine the sate of the service, OS it hosted on, dependant services like php or sql etc. Usually this gives us enough info to know when something's up. For http hosts we additionally monitor by checking http reponse code. Haven't add any for onion addresses assuming if plain works so should onion, though that wasn't the case. It's true we "rushed" pushing the tor related stuff because it was just embarissing how long it took (I made the initial issue as one of the first ones after we started disroot, so I know damn well how bad it feels). But thanks to your reporting and persistancy (I really enjoy it actually) things will get done right. So thanks for ass kicking and great work!
Author

Thanks; great. Always happy to see an "issue" turn into an epic with a dozen sub-issues :-)

Great to see the /en/tor page - what I suggest is beside the CHANGELOG on the footer of every page, link to /tor from "Tor Onion" It might allow you to do whatever your magic is to point to translations.

The link on the /tor page does NOT work
http://4dhkkxfcsvzvh3p5djkmuehhgd6t6l7wmzih6b4ss744hegwkiae7ad.onion/

Nor does the redirect.

**So one more issue to open please: ** Testing Tor.

You should be able to look for dead onion links on that test page the same way that you look for dead https: links. An easy way is to have a privoxy on your test machine that forwards .onion addresses to socks5:9050 and just run the testrunner pointing to the proxy.

What do you use as a testrunner?

Thanks; great. Always happy to see an "issue" turn into an epic with a dozen sub-issues :-) Great to see the /en/tor page - what I suggest is beside the CHANGELOG on the footer of every page, link to /tor from "Tor Onion" It might allow you to do whatever your magic is to point to translations. The link on the /tor page does NOT work http://4dhkkxfcsvzvh3p5djkmuehhgd6t6l7wmzih6b4ss744hegwkiae7ad.onion/ Nor does the redirect. **So one more issue to open please: ** Testing Tor. You should be able to look for dead onion links on that test page the same way that you look for dead https: links. An easy way is to have a privoxy on your test machine that forwards .onion addresses to socks5:9050 and just run the testrunner pointing to the proxy. What do you use as a testrunner?
Author

Mumble should be "easy" to set up and might be test next one to try. I may still be set up to help you test mumble over tor.

So one more issue to open please: Tor Mumble. Take over #576

Mumble should be "easy" to set up and might be test next one to try. I may still be set up to help you test mumble over tor. So one more issue to open please: Tor Mumble. Take over https://git.disroot.org/Disroot/Disroot-Project/issues/576
Author

So one more issue to open please: Tor /privatebin - take over #574

So one more issue to open please: Tor /privatebin - take over https://git.disroot.org/Disroot/Disroot-Project/issues/574
Owner

N.B.: clearnet https://disroot.org/en/nextcloud is 404

Not sure where you got that url from but it's invalid so doesnt work

So one more issue to open please: Tor /privatebin

There's nothing wrong with that so not sure what you refer to.

> N.B.: clearnet https://disroot.org/en/nextcloud is 404 Not sure where you got that url from but it's invalid so doesnt work > So one more issue to open please: Tor /privatebin There's nothing wrong with that so not sure what you refer to.
Owner

The link on the /tor page does NOT work

Fix pushed awaiting approval. Most probably live tomorrow.

> The link on the /tor page does NOT work Fix pushed awaiting approval. Most probably live tomorrow.
Author

Maybe open an other issue for: git.

When you are logged in as a user on git.disroot.org clearnet, go to an issue like /Disroot/Disroot-Project/issues/369 it takes you to http://kgtz2pmmov5jfvn3z4mqryffjnnw6krzrgxxoyaqhqckjrr4pckyhsqd.onion/Disroot/Disroot-Project/issues/5652

your logged in state is not preserved - you have to sign in on the onion. Maybe a cookies thing in gitea and not worth chasing

Maybe open an other issue for: git. When you are logged in as a user on git.disroot.org clearnet, go to an issue like /Disroot/Disroot-Project/issues/369 it takes you to http://kgtz2pmmov5jfvn3z4mqryffjnnw6krzrgxxoyaqhqckjrr4pckyhsqd.onion/Disroot/Disroot-Project/issues/5652 your logged in state is not preserved - you have to sign in on the onion. Maybe a cookies thing in gitea and not worth chasing
Author

Add a reference to the git onion on /en/tor.

Add a reference to the git onion on /en/tor.
meaz added a new dependency 2023-07-26 10:22:04 +02:00
meaz added a new dependency 2023-07-26 10:22:51 +02:00
meaz added a new dependency 2023-07-26 10:23:14 +02:00
meaz added a new dependency 2023-07-26 10:23:32 +02:00
meaz removed a dependency 2023-07-27 08:58:55 +02:00
meaz removed a dependency 2023-07-27 09:34:54 +02:00
Owner

@emdee we've changed the tor page: https://disroot.org/en/tor

@emdee we've changed the tor page: https://disroot.org/en/tor
Author

@meaz Thanks - it's very pretty, but
#578 might help it work better :-)

I added a simple script for basic testing.

@meaz Thanks - it's very pretty, but https://git.disroot.org/Disroot/Disroot-Project/issues/578 might help it work better :-) I added a simple script for basic testing.
Author

Could you add a comment here as to which services have been successfully tested.

I'll be very surprised (but delighted) if you got jitsi to work and I expect there's more to it than just a single front onion. Aren't there things like STUN addresses?

You may need to plan a layout on that page for more that just a simple link; for example SMTP/POP/IMAP will take a page of instructions...

Could you add a comment here as to which services have been successfully tested. I'll be very surprised (but delighted) if you got jitsi to work and I expect there's more to it than just a single front onion. Aren't there things like STUN addresses? You may need to plan a layout on that page for more that just a simple link; for example SMTP/POP/IMAP will take a page of instructions...
muppeth removed this from the 12.22 - December project 2023-11-08 23:29:24 +01:00
meaz removed this from the 12.22 - December milestone 2023-12-20 18:23:42 +01:00
muppeth added the
TOR
label 2024-03-03 12:02:36 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: Disroot/Disroot-Project#369
No description provided.