# Security Guide needs maintenance

**URL:** <https://discuss.rubyonrails.org/t/security-guide-needs-maintenance/66485>\
**Category:** rubyonrails-talk\
**Created:** [March 2, 2013, 9:15am UTC](https://discuss.rubyonrails.org/t/security-guide-needs-maintenance/66485 "2013-03-02T09:15:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Frederick\_Cheung](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/frederick_cheung/32/3901_2.png) [@Frederick\_Cheung](https://discuss.rubyonrails.org/u/Frederick_Cheung)\
**Post date:** [March 2, 2013, 9:15am UTC](https://discuss.rubyonrails.org/t/security-guide-needs-maintenance/66485/1 "2013-03-02T09:15:28Z")

</div>

With the default cookie store the cookie value is the session data so what becomes important is the cookie signing which I believe is a sha1 hmac by default) The rails guides (and all the docs in general) are managed via [https://github.com/lifo/docrails](https://github.com/lifo/docrails)

Open a pull request there and someone from the docs team will review it (and then generally give you commit rights). Docrails and rails itself are then synced periodically.

Fred.