Host core services as tor onion services #3
Labels
No Label
FCKPTN
WIP
bug
docs done
docs needed
duplicate
enhancement
feature
gemini
invalid
legal-ish
needs help
onionz
proposal
question
resolved
security
spam
todo
upstream-related
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Depends on
#5 DroneCI as onion service connected to onion gitea
dotya.ml/community
#22 Menu items in the issue menu are not onionized
dotya.ml/community
#23 Status button in a footer is not onionized
dotya.ml/community
Reference: dotya.ml/community#3
Loadingβ¦
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
While both Gitea and Drone rely in part on
js
, it is still possible that some users would prefer to connect to us using tor (possibly withjs
whitelisted here).I propose we make our core services available as onion services, too.
current progress
edit:
after this is concluded, we could apply to add the services to the WeSupportTor list https://trac.torproject.org/projects/tor/wiki/org/projects/WeSupportTor
as also mentioned in 39a5ba03c8 and thanks to @kreyren π we now have both the homepage and gitea available as onion services.
homepage: http://6426tqrh4y5uobmo5y2csaip3m3avmjegd2kpa24sadekpxglbm34aqd.onion
gitea: http://2crftbzxbcoqolvzreaaeyrod5qwycayef55gxgzgfcpqlaxrnh3kkqd.onion
prometheus: http://vognfwm7c6wq2gxqcmswi2flwckuxryefd7n3axxkvlpasdjhns5buqd.onion
grafana: http://6t3ydf7sl7iso2wbymbfjtaq6qqlrms37ffik2siulsljc3ubobklnid.onion
statuspage: http://o4irro4dspyuytbw2b2g2ac4ukkh2ex53oolhzw7hrfjmq6tiklrtwqd.onion/
more on this, including what's up with hidden drone:
https://dotya.ml/about/#onion-serviceshttp://6426tqrh4y5uobmo5y2csaip3m3avmjegd2kpa24sadekpxglbm34aqd.onion/about/#onion-services
UPDATE 2022-08-30: now available at https://dotya.ml/onions/ and http://6426tqrh4y5uobmo5y2csaip3m3avmjegd2kpa24sadekpxglbm34aqd.onion/onions/, respectively.
edit: note that ssh is also enabled for gitea via tor
What is the status on this in terms of gitea handling? Seems that gitea needs adaptation to replace the domain with onions when accessed from onions -> Create tracking of what is needed in upstream willing to consider contribs
@kreyren
As you say, the only thing that prevents you from functioning easily on Gitea via tor is Gitea using absolute link paths at certain places - using relative (as in
/user/whateverrepo/commits/...
) links would solve this. Also, a parameter DOMAIN is set in app.ini config, which would need to either be handled differently or something..this gets used in the displayed cloning URL etc. These I can think of off the top of my head atm, there are probably more (e.g. zeripath - one of the Gitea maintainers - mentioned email links)@wanderer So what's preventing you from submitting upstream tracking?