Name |
Last commit
|
Last update |
---|---|---|
.. | ||
applications | ||
concerns | ||
platforms | ||
providers | ||
cluster.rb | ||
project.rb |
BigW Consortium Gitlab
attr_encrypted does different things with `key` depending on what mode you are using: 1. In `:per_attribute_iv_and_salt` mode, it generates a hash with the salt: https://github.com/attr-encrypted/encryptor/blob/c3a62c4a9e74686dd95e0548f9dc2a361fdc95d1/lib/encryptor.rb#L77. There is no need to truncate the key to 32 bytes here. 2. In `:per_attribute_iv` mode, it sets the key directly to the password, so truncation to 32 bytes is necessary. Closes #47166
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
applications | Loading commit data... | |
concerns | Loading commit data... | |
platforms | Loading commit data... | |
providers | Loading commit data... | |
cluster.rb | Loading commit data... | |
project.rb | Loading commit data... |