gitea/gitea.com
42
8
Issues 8 Activity

HTTP and SSH are inaccessible using Tor (HTTPS works) #15

New Issue
Open
opened 2020-07-17 11:12:26 +00:00 by wildfox · 5 comments
wildfox commented 2020-07-17 11:12:26 +00:00
Copy Link

The HTTP and SSH ports are (effectively) inaccessible to Tor users.

This means Tor users who type in gitea.com see "The connection was reset" (not redirected to HTTPS); and cannot use SSH to fetch and push their code.

Fortunately HTTPS works as expected and application tokens may be used instead of passwords; but the application token is more powerful than an SSH key.

Gitea is awesome! Thank you.

The HTTP and SSH ports are (effectively) inaccessible to Tor users. This means Tor users who type in `gitea.com` see "The connection was reset" (not redirected to HTTPS); and cannot use SSH to fetch and push their code. Fortunately HTTPS works as expected and application tokens may be used instead of passwords; but the application token is more powerful than an SSH key. Gitea is awesome! Thank you.
6543 added the
bug
 label 2020-07-17 11:13:37 +00:00
6543 commented 2020-07-17 11:13:49 +00:00
Owner
Copy Link

can confirm http

can confirm http
👍 1
6543 commented 2020-07-17 15:58:41 +00:00
Owner
Copy Link

if https://github.com/EFForg/https-everywhere/issues/19397 is acepted it will at least partialy fix the problem

if https://github.com/EFForg/https-everywhere/issues/19397 is acepted it will at least partialy fix the problem
wildfox commented 2020-07-17 22:23:00 +00:00
Author
Copy Link

Haha. Yes, I suppose that'll help the HTTP case indeed. Though I think SSH is the bigger issue here.

Haha. Yes, I suppose that'll help the HTTP case indeed. Though I think SSH is the bigger issue here.
lunny commented 2020-07-18 03:00:30 +00:00
Owner
Copy Link

Yes, SSH is a problem.

Yes, SSH is a problem.
6543 commented 2020-07-22 14:37:31 +00:00
Owner
Copy Link

was https://github.com/EFForg/https-everywhere/pull/19398 merged, so now only SSH problem has to be solfed

was https://github.com/EFForg/https-everywhere/pull/19398 merged, so now only SSH problem has to be solfed
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
No results found.
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
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.

Dependencies

No dependencies set.

Reference: gitea/gitea.com#15
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?