BigW Consortium Gitlab
Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
gitlab-ce
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Forest Godfrey
gitlab-ce
Commits
f8bd8f4f
Commit
f8bd8f4f
authored
Jun 01, 2018
by
Robert Speicher
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'sh-add-ruby-2.4-comment' into 'master'
Add comment about the need for truncating keys in Ruby 2.4 See merge request gitlab-org/gitlab-ce!19330
parents
2de002b3
78d78ad1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
0 deletions
+7
-0
settings.rb
config/settings.rb
+7
-0
No files found.
config/settings.rb
View file @
f8bd8f4f
...
@@ -85,7 +85,14 @@ class Settings < Settingslogic
...
@@ -85,7 +85,14 @@ class Settings < Settingslogic
File
.
expand_path
(
path
,
Rails
.
root
)
File
.
expand_path
(
path
,
Rails
.
root
)
end
end
# Returns a 256-bit key for attr_encrypted
def
attr_encrypted_db_key_base
def
attr_encrypted_db_key_base
# Ruby 2.4+ requires passing in the exact required length for OpenSSL keys
# (https://github.com/ruby/ruby/commit/ce635262f53b760284d56bb1027baebaaec175d1).
# Previous versions quietly truncated the input.
#
# The default mode for the attr_encrypted gem is to use a 256-bit key.
# We truncate the 128-byte string to 32 bytes.
Gitlab
::
Application
.
secrets
.
db_key_base
[
0
..
31
]
Gitlab
::
Application
.
secrets
.
db_key_base
[
0
..
31
]
end
end
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment