7351a484d7
|
||
|---|---|---|
| .. | ||
| img | ||
| README.md | ||
| asset_proxy.md | ||
| crime_vulnerability.md | ||
| information_exclusivity.md | ||
| password_length_limits.md | ||
| password_storage.md | ||
| rack_attack.md | ||
| rate_limits.md | ||
| reset_root_password.md | ||
| ssh_keys_restrictions.md | ||
| two_factor_authentication.md | ||
| unlock_user.md | ||
| user_email_confirmation.md | ||
| user_file_uploads.md | ||
| webhooks.md | ||
README.md
| comments | type |
|---|---|
| false | index |
Security
- Password storage
- Password length limits
- Restrict SSH key technologies and minimum length
- Rate limits
- Webhooks and insecure internal web services
- Information exclusivity
- Reset your root password
- Unlock a locked user
- User File Uploads
- How we manage the CRIME vulnerability
- Enforce Two-factor authentication
- Send email confirmation on sign-up
- Security of running jobs
- Proxying images
Securing your GitLab installation
To make sure your GitLab instance is safe and secure, please consider implementing Sign up restrictions to avoid malicious users creating accounts.