github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Prevent logging of IP addresses #15041

New Issue
Closed
opened 2025-11-02 11:28:46 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 11:28:46 -06:00
Owner
Copy Link

Originally created by @sokai on GitHub (Oct 20, 2025).

Feature Description

Hey,

I stumbled over the fact, that it seems not possible to prevent logging of full IP addresses in the logs.

This an example log clip (w/ some redactions):

[…]
[…] Accepted publickey for git from IP_ALLOWED port 33330 ssh2: ED25519 SHA256:+REDACTED
[…] Received disconnect from IP_ALLOWED port 33330:11: disconnected by user
[…] Disconnected from user git IP_ALLOWED port 33330
[…] Invalid user www-data from 142.93.X.X port 33436
[…] Invalid user deploy from 49.204.X.X port 52108
[…] Received disconnect from 49.204.X.X port 52108:11: Bye Bye [preauth]
[…] Disconnected from invalid user deploy 49.204.X.X port 52108 [preauth]
[…] Connection closed by invalid user www-data 142.93.X.X port 33436 [preauth]
[…] Invalid user zs from 59.3.X.X port 50206
[…] Received disconnect from 59.3.X.X port 50206:11: Bye Bye [preauth]
[…] Disconnected from invalid user zs 59.3.X.X port 50206 [preauth]

… with this config:

[log]
LEVEL = Warn
MODE = console

Question/Request: Is it possible (= may it become possible) to prevent logging of full IP addresses?
(Reason: I'd like to only log IP address subnets – e. g. 59.3.0.0 – to be GDPR compliant …)

Thanks an KR!

Screenshots

No response

Originally created by @sokai on GitHub (Oct 20, 2025). ### Feature Description Hey, I stumbled over the _fact_, that it seems not possible to prevent logging of full IP addresses in the logs. This an example log clip (w/ some redactions): ```logs […] […] Accepted publickey for git from IP_ALLOWED port 33330 ssh2: ED25519 SHA256:+REDACTED […] Received disconnect from IP_ALLOWED port 33330:11: disconnected by user […] Disconnected from user git IP_ALLOWED port 33330 […] Invalid user www-data from 142.93.X.X port 33436 […] Invalid user deploy from 49.204.X.X port 52108 […] Received disconnect from 49.204.X.X port 52108:11: Bye Bye [preauth] […] Disconnected from invalid user deploy 49.204.X.X port 52108 [preauth] […] Connection closed by invalid user www-data 142.93.X.X port 33436 [preauth] […] Invalid user zs from 59.3.X.X port 50206 […] Received disconnect from 59.3.X.X port 50206:11: Bye Bye [preauth] […] Disconnected from invalid user zs 59.3.X.X port 50206 [preauth] ``` … with this config: ```ini [log] LEVEL = Warn MODE = console ``` **Question**/_Request_: Is it possible _(= may it become possible)_ to prevent logging of full IP addresses? (Reason: I'd like to only log IP address subnets – e. g. `59.3.0.0` – to _be GDPR compliant_ …) Thanks an KR! ### Screenshots _No response_
GiteaMirror added the type/question label 2025-11-02 11:28:46 -06:00
GiteaMirror commented 2025-11-02 11:28:47 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Oct 20, 2025):

This is due to SSHD logging that it's showing up. If you don't want SSHD to output this information you are able to use the rootless image.

@techknowlogick commented on GitHub (Oct 20, 2025): This is due to SSHD logging that it's showing up. If you don't want SSHD to output this information you are able to use the rootless image.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#15041
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?