Project

General

Profile

Actions

Refactor #7570

closed

set secret_key_base for rails 6.0 upgrade

Added by Joseph Magen almost 10 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Rails
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Related issues 5 (0 open5 closed)

Related to Foreman - Tracker #15715: Rails 5.0 upgrade tasksResolved07/18/2016

Actions
Related to Foreman - Tracker #20948: Rails 5.1 upgrade tasksClosed09/16/2017

Actions
Related to Foreman - Tracker #21834: Rails 5.2 upgrade tasksClosed

Actions
Has duplicate Foreman - Refactor #14022: secret_key_base should be configuredDuplicate03/02/2016Actions
Blocks Foreman - Tracker #24837: Rails 6.0 TrackerClosed

Actions
Actions #1

Updated by Joseph Magen almost 10 years ago

http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html

Rails 4.0 encrypts the contents of cookie-based sessions if secret_key_base has been set. Rails 3.x signed, but did not encrypt, the contents of cookie-based session. Signed cookies are "secure" in that they are verified to have been generated by your app and are tamper-proof. However, the contents can be viewed by end users, and encrypting the contents eliminates this caveat/concern without a significant performance penalty.

Actions #2

Updated by Brandon Weeks over 8 years ago

Actions #3

Updated by Dominic Cleal over 8 years ago

  • Blocked by deleted (Refactor #14022: secret_key_base should be configured)
Actions #4

Updated by Dominic Cleal over 8 years ago

  • Has duplicate Refactor #14022: secret_key_base should be configured added
Actions #5

Updated by Anonymous almost 7 years ago

Actions #6

Updated by Anonymous almost 7 years ago

Actions #7

Updated by Anonymous over 6 years ago

Actions #8

Updated by Anonymous over 6 years ago

  • Tracker changed from Bug to Refactor
  • Subject changed from set secret_key_base for rails 4 upgrade to set secret_key_base for rails 6.0 upgrade
Actions #9

Updated by Anonymous almost 6 years ago

Actions #10

Updated by Anonymous almost 6 years ago

Actions #11

Updated by Anonymous almost 6 years ago

Actions #12

Updated by The Foreman Bot over 4 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Tomer Brisker
  • Pull request https://github.com/theforeman/foreman/pull/7285 added
Actions #13

Updated by The Foreman Bot over 4 years ago

  • Fixed in Releases 2.0.0 added
Actions #14

Updated by Tomer Brisker over 4 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF