general security question #822

New Issue

GiteaMirror · 2025-11-02T03:37:50-06:00

GiteaMirror commented

2025-11-02 03:37:50 -06:00

Originally created by @laoshaw on GitHub (Jun 18, 2017).

How safe is it to run gitea on a public IP? comparing to gitlab, redmine etc? https will be used, but how secure is it overall?

I use it locally and really like its simplicity and light-weight-ness, but do not know how many are using it in a public IP these days.

Originally created by @laoshaw on GitHub (Jun 18, 2017). How safe is it to run gitea on a public IP? comparing to gitlab, redmine etc? https will be used, but how secure is it overall? I use it locally and really like its simplicity and light-weight-ness, but do not know how many are using it in a public IP these days.

GiteaMirror added the type/question label 2025-11-02 03:37:50 -06:00

GiteaMirror closed this issue

2025-11-02 03:37:51 -06:00

GiteaMirror commented

2025-11-02 03:37:51 -06:00

@lafriks commented on GitHub (Jun 18, 2017):

I think it should be quite safe, I have been running it on public IP for quite some time

@lafriks commented on GitHub (Jun 18, 2017): I think it should be quite safe, I have been running it on public IP for quite some time

GiteaMirror commented

2025-11-02 03:37:52 -06:00

@lunny commented on GitHub (Jun 19, 2017):

I have two instances on public IP. I think it's safe enough!

@lunny commented on GitHub (Jun 19, 2017): I have two instances on public IP. I think it's safe enough!

GiteaMirror commented

2025-11-02 03:37:52 -06:00

@bkcsoft commented on GitHub (Jun 19, 2017):

Apart from try.gitea.io, I host 3 ipublic nstances personally, and have 3 other friends that have public instances as well. I'd deem it "safe enough" 🙂

@bkcsoft commented on GitHub (Jun 19, 2017): Apart from `try.gitea.io`, I host 3 ipublic nstances personally, and have 3 other friends that have public instances as well. I'd deem it "safe enough" 🙂

GiteaMirror commented

2025-11-02 03:37:52 -06:00

@ulm0 commented on GitHub (Jun 19, 2017):

I've been using it for a while now on public ip, 0 problems.

@ulm0 commented on GitHub (Jun 19, 2017): I've been using it for a while now on public ip, 0 problems.

GiteaMirror commented

2025-11-02 03:37:52 -06:00

@sapk commented on GitHub (Jun 19, 2017):

Same here, running it on public IP no problem. It would be good to have a security audit in the future. We could also require some version of tools (or display warning) used by gitea like openssh based on CVE.

@sapk commented on GitHub (Jun 19, 2017): Same here, running it on public IP no problem. It would be good to have a security audit in the future. We could also require some version of tools (or display warning) used by gitea like openssh based on CVE.

GiteaMirror commented

2025-11-02 03:37:52 -06:00

@pgaskin commented on GitHub (Jun 20, 2017):

4 public, 1 private, running for a while, no problems.

@pgaskin commented on GitHub (Jun 20, 2017): 4 public, 1 private, running for a while, no problems.

GiteaMirror commented

2025-11-02 03:37:52 -06:00

@techknowlogick commented on GitHub (May 10, 2018):

Can this issue be closed?

@techknowlogick commented on GitHub (May 10, 2018): Can this issue be closed?

GiteaMirror referenced this issue

2025-11-02 06:09:19 -06:00