The secret key generator, for the forgery protection, was a nice addition. I've added a rake task that will use that generator to generate a new key - rake secret:generate:key
patch: http://dev.rubyonrails.org/ticket/10363
thoughts, +1's...
The secret key generator, for the forgery protection, was a nice addition. I've added a rake task that will use that generator to generate a new key - rake secret:generate:key
What are the use cases for generating a new key? (not being contentious, just can't think of any off hand)
I'd imagine it might be useful for people who're migrating from 1.2.x to 2.0 ?
I'm thinking about the people who will be migrating from rails 1.x.x version to 2.0 and want to take advantage of the forgery protection in their existing application(s).
DHH wrote:
Our development team doesn't use the rails generator when producing a new project. Instead, we've got a system that copies the SVN repository for a blank-slate project over to the new one. Having a secret key generator would be very useful for us. From what I've heard, this isn't an uncommon scenario.
Cheers, Tammer
I usually need this functionality for creating a custom Staging environment or for other cases in an app when I need a random key. It's also pretty easy to open up irb and do it myself, but I could see it being helpful to someone who's new to Ruby.
-tieg
Just wanted to bump this one up, case the core team forgot about it during all their work for the 2.0 release. We have 3 +1's and I've implemented bitsweat's suggestions.
Robert
tzaharia wrote: