mathias/gitea-mcp
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

auth: no audit logging of authentication failures #9

New Issue
Open
opened 2026-05-14 08:44:17 +00:00 by mathias · 0 comments
mathias commented 2026-05-14 08:44:17 +00:00
Owner
Copy Link

Failed auth attempts are silently dropped — no structured log entry, no forensic trail. Impossible to distinguish a misconfigured client from a brute-force attempt after the fact.

File: internal/auth/bearer.go:22-42

Suggestion: On every 401, emit a structured log line with:

  • Failure reason (jwt_invalid, jwt_dex_unavailable, static_token_mismatch, no_token)
  • Remote IP
  • Token type attempted (JWT vs static)
  • First 8 chars of the presented token (enough to correlate client, not enough to reconstruct)
  • Timestamp
Failed auth attempts are silently dropped — no structured log entry, no forensic trail. Impossible to distinguish a misconfigured client from a brute-force attempt after the fact. **File:** `internal/auth/bearer.go:22-42` **Suggestion:** On every 401, emit a structured log line with: - Failure reason (`jwt_invalid`, `jwt_dex_unavailable`, `static_token_mismatch`, `no_token`) - Remote IP - Token type attempted (JWT vs static) - First 8 chars of the presented token (enough to correlate client, not enough to reconstruct) - Timestamp
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
mathias
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mathias/gitea-mcp#9
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?