Anonymity - Gitea .onion setup (Code repositories) #22

Open
opened 2024-09-17 20:34:39 +02:00 by nihilist · 5 comments
Owner
No description provided.
nihilist added this to the OPSEC Tutorials (paid contributions) project 2024-09-17 20:34:39 +02:00
Author
Owner

Assigned to daybreak
price: 40 euros
deadline: 14th October

Assigned to daybreak price: 40 euros deadline: 14th October
nihilist added the
Complex
label 2024-09-23 10:31:29 +02:00
Author
Owner

past deadline, unassigning

past deadline, unassigning
nihilist added the
/!\ On Priority - High Quality Tutorial
label 2024-10-15 13:30:13 +02:00
Author
Owner

requires #13 to be finished
optional: #66 to be finished in the case of an on-premise setup

to be explained:

  • why this is important (explain what happened to tornadocash) >> a clear attack on free speech. Anonymity is REQUIRED even for free speech
  • what git is: decentralised protocol for project management, but the most popular place for git repositories is owned by microsoft, a centralised entity working for the US government. >> mention what happened to the tornadocash github repositories
  • what is gitea: essentially a github replacement, that way the repositories you have there can't be taken down without your own accord.
  • and if the server is accessible only via .onion, then authorities can't even tell where the server is, making your free speech on it unstoppable.

to be showcased:

  • how to setup a gitea instance, accessible only over .onion (no clearnet at all!)
  • how to create a repository, how to git pull it (via the .onion domain) and send commits to it (git commit and such) via Tor still. from a whonix VM. (need to mention how git can interact with the local socks5 proxy of Tor)
  • how to disable registrations, it must be manual (people contact you on simplex to ask you to create an account for them) >> as email registration is unacceptable

POTENTIALLY COMPLEX PART:

  • showcase how to update the gitea service while still going through Tor (docker-compose pull to make it simple)
  • showcase how you can MIRROR github repositories on your gitea, while also going through Tor (serverside socks5 proxying gitea config: https://github.com/go-gitea/gitea/issues/22335 ?)
requires https://git.nowhere.moe/nihilist/blog-contributions/issues/13 to be finished optional: https://git.nowhere.moe/nihilist/blog-contributions/issues/66 to be finished in the case of an on-premise setup to be explained: - why this is important (explain what happened to tornadocash) >> a clear attack on free speech. Anonymity is REQUIRED even for free speech - what git is: decentralised protocol for project management, but the most popular place for git repositories is owned by microsoft, a centralised entity working for the US government. >> mention what happened to the tornadocash github repositories - what is gitea: essentially a github replacement, that way the repositories you have there can't be taken down without your own accord. - and if the server is accessible only via .onion, then authorities can't even tell where the server is, making your free speech on it unstoppable. to be showcased: - how to setup a gitea instance, accessible only over .onion (no clearnet at all!) - how to create a repository, how to git pull it (via the .onion domain) and send commits to it (git commit and such) via Tor still. from a whonix VM. (need to mention how git can interact with the local socks5 proxy of Tor) - how to disable registrations, it must be manual (people contact you on simplex to ask you to create an account for them) >> as email registration is unacceptable POTENTIALLY COMPLEX PART: - showcase how to update the gitea service while still going through Tor (docker-compose pull to make it simple) - showcase how you can MIRROR github repositories on your gitea, while also going through Tor (serverside socks5 proxying gitea config: https://github.com/go-gitea/gitea/issues/22335 ?)

I volunteer to do this one.

I volunteer to do this one.
Author
Owner

ok, assigning it to you then, thx.

assigned to: baz
price: 40 euros
deadline: 20th November

ok, assigning it to you then, thx. assigned to: baz price: 40 euros deadline: 20th November
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: nihilist/blog-contributions#22
No description provided.