kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity

[ci skip] Clarity about embed metadata in signed and encrypted cookie

Browse source
This commit is contained in:
Vishal Telangre 2019-05-11 20:27:44 +05:30
parent e8350663ad
commit 739aec916f
No known key found for this signature in database
GPG key ID: 16BA3EBD701E48D8
2 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
guides/source/6_0_release_notes.md
View file

@ -245,7 +245,7 @@ Please refer to the [Changelog][action-pack] for detailed changes.
* Expose `ActionController::Parameters#each_key`.
([Pull Request](https://github.com/rails/rails/pull/33758))
* Add purpose metadata to signed/encrypted cookies to prevent copying the value of
* Add purpose and expiry metadata inside signed/encrypted cookies to prevent copying the value of
cookies into one another.
([Pull Request](https://github.com/rails/rails/pull/32937))

7
guides/source/upgrading_ruby_on_rails.md
View file

@ -85,13 +85,14 @@ Rails 6.1. You are encouraged to enable `config.force_ssl` to enforce HTTPS
connections throughout your application. If you need to exempt certain endpoints
from redirection, you can use `config.ssl_options` to configure that behavior.
### Purpose in signed or encrypted cookie is now embedded within cookies
### Purpose and expiry metadata is now embedded inside signed and encrypted cookies for increased security
To improve security, Rails embeds the purpose and expiry metadata inside encrypted or signed cookies value.
To improve security, Rails embeds the purpose information in encrypted or signed cookies value.
Rails can then thwart attacks that attempt to copy the signed/encrypted value
of a cookie and use it as the value of another cookie.
This new embed information make those cookies incompatible with versions of Rails older than 6.0.
This new embed metadata make those cookies incompatible with versions of Rails older than 6.0.
If you require your cookies to be read by Rails 5.2 and older, or you are still validating your 6.0 deploy and want
to be able to rollback set