2019-08-21 21:49:04 +00:00
---
2021-05-27 03:10:55 +00:00
stage: Manage
2022-01-27 03:14:06 +00:00
group: Authentication and Authorization
2020-11-26 06:09:20 +00:00
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2019-08-21 21:49:04 +00:00
type: reference
---
2021-05-27 03:10:55 +00:00
# Password storage **(FREE)**
2019-08-21 21:49:04 +00:00
2021-06-08 00:10:34 +00:00
GitLab stores user passwords in a hashed format to prevent passwords from being
stored as plain text.
2019-08-21 21:49:04 +00:00
2021-06-08 00:10:34 +00:00
GitLab uses the [Devise ](https://github.com/heartcombo/devise ) authentication
library to hash user passwords. Created password hashes have these attributes:
2019-08-21 21:49:04 +00:00
2021-06-08 00:10:34 +00:00
- **Hashing**: The [`bcrypt` ](https://en.wikipedia.org/wiki/Bcrypt ) hashing
function is used to generate the hash of the provided password. This is a
strong, industry-standard cryptographic hashing function.
- **Stretching**: Password hashes are [stretched ](https://en.wikipedia.org/wiki/Key_stretching )
to harden against brute-force attacks. By default, GitLab uses a stretching
factor of 10.
- **Salting**: A [cryptographic salt ](https://en.wikipedia.org/wiki/Salt_(cryptography ))
is added to each password to harden against pre-computed hash and dictionary
attacks. To increase security, each salt is randomly generated for each
password, with no two passwords sharing a salt.
