News for hackers. Stuff that matters.
Re:Reminder: secret_token.rb is named so for a reason by ajross on Wednesday December 26, 2012 @01:52PM (#4970347)
How is this not considered a framework bug? "Secret tokens" are project-specific configuration more or less by definition. Putting them in something that lives in a source directory is simply asking for this kind of mistake.

Rails deployments aren't leaking their ssh keys or database content because that is stored separately. To paraphrase the title: these things are stored separately for a reason.

Get this thing out of the source, guys.

Re:Reminder: secret_token.rb is named so for a reason by kawsper on Wednesday December 26, 2012 @07:12PM (#4971651)
database.yml is also placed in config-directory.

secret_token.rb is placed where it is, because it is a initializer.

http://guides.rubyonrails.org/configuring.html#locations-for...

Re:Reminder: secret_token.rb is named so for a reason by ajross on Thursday December 27, 2012 @04:15PM (#4975067)
How is "because it is a initializer" a response to the point? The fact that it is implemented as Ruby code has nothing to do with whether or not it should be stored in a source code directory. Clearly it should not. Yet it is. That's a framework bug.