Skip to content

Raise failed authentication log entry to warning #3713

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Darcara opened this issue Mar 23, 2018 · 3 comments · Fixed by #3726
Closed

Raise failed authentication log entry to warning #3713

Darcara opened this issue Mar 23, 2018 · 3 comments · Fixed by #3726
Labels
type/enhancement An improvement of existing functionality type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@Darcara
Copy link

Darcara commented Mar 23, 2018

  • On Gitea version: 1.4.0+rc3
  • Database: MySQL

Description

Currently failed authentication attempts are logged as info into gitea.log.
All executed SQL queries are also logged as info into xorm.log which means increases file size and disk writes.
In order to avoid the size and write problem I have increased log level to warn, but that leaves my fail2ban without the required log lines.

Alternatively add an option to disable the xorm log, or log executed SQL queries as debug, which should be better for production servers with several active users.

As an aside it would be nice to have a log of failed password reset requests .

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Mar 24, 2018
@mckaygerhard
Copy link

related to the #2512 fiuuu from number 2XXX to 3XXX and still not reolved.. amount of 100 issues happened!? seems gitea development features raises mor and more bugs?

@lunny lunny added the type/enhancement An improvement of existing functionality label Mar 30, 2018
@lunny
Copy link
Member

lunny commented Mar 30, 2018

@Darcara As an aside it would be nice to have a log of failed password reset requests . is not resolved by #3726. Maybe you could create a new issue to describe that or I will reopen this one.

@Darcara
Copy link
Author

Darcara commented Mar 30, 2018

I made #3745 and thanks for your fast work, much appreciated :)

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/enhancement An improvement of existing functionality type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants