Paul Nothaft
0205c7dcce
Repo transferred from the-luap/picpeak → PicPeak/picpeak. Docker images
publish to ghcr.io/picpeak/picpeak/{backend,frontend} (lowercase, per the
GHCR canonical form computed by docker-build.yml's `${GITHUB_REPOSITORY,,}`).
Sweep covers:
- docker-compose.production.yml + Dockerfiles → new image registry path
- README, CONTRIBUTING, SECURITY, SIMPLE_SETUP, scripts/picpeak-setup.sh
→ new GitHub URLs
- Update-check / release-notes services (updateCheckService,
environmentService, updateNotificationService, adminSystem,
UpdateNotification, githubReleaseUrl) → GitHub API + tag URLs use the
canonical PicPeak/picpeak path
- Issue templates + README-DOCKER + workflow README → updated package URLs
- One commit-context comment in migrations/090 + customerAccountsService
CHANGELOG.md is intentionally untouched (historical release entries are
immutable; GitHub auto-redirects the old URLs indefinitely).
CLAUDE.md keeps the bare `(the-luap)` reference — that's the maintainer's
personal handle, not a repo URL.
22 files, 48/48 line swaps (every change is a 1:1 URL replacement).
88 lines
2.7 KiB
Markdown
88 lines
2.7 KiB
Markdown
# Security Policy
|
|
|
|
## Supported Versions
|
|
|
|
We release patches for security vulnerabilities. Currently supported versions:
|
|
|
|
| Version | Supported |
|
|
| ------- | ------------------ |
|
|
| 2.x.x | :white_check_mark: |
|
|
| < 2.0 | :x: |
|
|
|
|
## Reporting a Vulnerability
|
|
|
|
We take the security of PicPeak seriously. If you have discovered a security vulnerability, please follow these steps:
|
|
|
|
### 1. **Do NOT create a public GitHub issue**
|
|
|
|
### 2. Report the vulnerability privately by:
|
|
- **Preferred:** Use [GitHub Private Vulnerability Reporting](https://github.com/PicPeak/picpeak/security/advisories/new)
|
|
- **Alternative:** Email us at **info@picpeak.app** with the details
|
|
- Include:
|
|
- Description of the vulnerability
|
|
- Steps to reproduce
|
|
- Potential impact
|
|
- Suggested fix (if any)
|
|
|
|
### 3. You can expect:
|
|
- Acknowledgment within 48 hours
|
|
- Regular updates on our progress
|
|
- Credit in the fix announcement (unless you prefer to remain anonymous)
|
|
|
|
## Security Measures
|
|
|
|
PicPeak implements several security measures:
|
|
|
|
### Authentication & Authorization
|
|
- JWT-based authentication with secure token storage
|
|
- bcrypt password hashing with configurable rounds
|
|
- Role-based access control for admin functions
|
|
- Session timeout management
|
|
|
|
### Input Validation
|
|
- All user inputs are validated and sanitized
|
|
- SQL injection prevention through parameterized queries
|
|
- XSS protection via Content Security Policy
|
|
- File upload restrictions and validation
|
|
|
|
### Rate Limiting
|
|
- API rate limiting to prevent abuse
|
|
- Brute force protection on authentication endpoints
|
|
- Configurable limits per endpoint
|
|
|
|
### Data Protection
|
|
- HTTPS enforcement in production
|
|
- Secure cookie settings
|
|
- CORS configuration
|
|
- Sensitive data encryption
|
|
|
|
### Infrastructure
|
|
- Regular dependency updates
|
|
- Security headers (HSTS, X-Frame-Options, etc.)
|
|
- Activity logging for audit trails
|
|
- Automated backups
|
|
|
|
## Best Practices for Deployment
|
|
|
|
1. **Always use HTTPS** in production
|
|
2. **Change default passwords** immediately
|
|
3. **Keep dependencies updated** regularly
|
|
4. **Configure firewall rules** appropriately
|
|
5. **Monitor logs** for suspicious activity
|
|
6. **Backup regularly** and test restoration
|
|
|
|
## Vulnerability Disclosure
|
|
|
|
We believe in responsible disclosure. Once a vulnerability is fixed:
|
|
|
|
1. We'll publish a security advisory
|
|
2. Credit researchers (with permission)
|
|
3. Detail the impact and mitigation steps
|
|
4. Release patches for all supported versions
|
|
|
|
## Contact
|
|
|
|
- Security issues: Email **info@picpeak.app** or use [GitHub Private Vulnerability Reporting](https://github.com/PicPeak/picpeak/security/advisories/new)
|
|
- General support: [GitHub Issues](https://github.com/PicPeak/picpeak/issues)
|
|
|
|
Thank you for helping keep PicPeak and its users safe! |