paul
1773ed5f95
Mirror to GitHub / mirror (push) Successful in 26s
Test and Lint / backend-test (push) Successful in 1m11s
continuous-integration/drone/push Build is passing
Test and Lint / frontend-test (push) Successful in 2m28s
Version and Release / version-bump (push) Successful in 32s
Version and Release / trigger-drone (push) Has been skipped
Original: feat: enhance security logging and ensure rate limit blocks are properly tracked - Add comprehensive logging for rate limit blocks with full request details - IP address (with proper proxy detection), user agent, headers, timestamps - Rate limit info (current count, limit, remaining, reset time) - Separate tracking for auth vs general endpoints - Enhance authentication failure logging - JWT validation failures with detailed error info - Admin auth attempts without token - Failed token validation with user context - All events include IP, path, method, user agent - Improve Winston logger configuration for production - Add automatic log rotation (10MB errors, 50MB combined) - Create separate security.log for auth/rate limit events - Ensure logs directory exists automatically - Add structured JSON format for log aggregation - Support container logging with LOG_TO_CONSOLE env var - Create comprehensive documentation - Security logging guide with examples - Monitoring recommendations - Configuration reference - Add test script to verify logging functionality All rate limit settings remain configurable via admin panel: - Window duration, max requests, auth limits - Skip authenticated requests option - Public endpoints only option 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
37 lines
868 B
Markdown
37 lines
868 B
Markdown
---
|
|
name: Security Vulnerability
|
|
about: Report security issues privately
|
|
title: '[SECURITY] '
|
|
labels: 'security'
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
⚠️ **IMPORTANT: For serious security vulnerabilities, please DO NOT create a public issue.**
|
|
|
|
Instead, please email security@example.com with the details.
|
|
|
|
For minor security improvements or questions, you can use this template:
|
|
|
|
**Type of Security Issue**
|
|
- [ ] Authentication/Authorization
|
|
- [ ] Data Exposure
|
|
- [ ] Input Validation
|
|
- [ ] Configuration Issue
|
|
- [ ] Dependency Vulnerability
|
|
- [ ] Other: ___________
|
|
|
|
**Description**
|
|
Brief description of the security concern.
|
|
|
|
**Impact**
|
|
What could an attacker potentially do?
|
|
|
|
**Steps to Reproduce**
|
|
If applicable, how can this be reproduced?
|
|
|
|
**Suggested Fix**
|
|
If you have ideas on how to fix this issue.
|
|
|
|
**References**
|
|
Any relevant security advisories, CVEs, or documentation. |