Closed dnrce closed 5 years ago
On March 3, 2008 at 03:33:39 (-0700), Anonymous commented:
Would it need something like
http://dev.rubyonrails.org/svn/rails/plugins/ssl_requirement/README
On March 3, 2008 at 09:23:53 (-0700), Anonymous commented:
You can also put apache in front of tracks (proxy) and use it to handle SSL. (Using apache for static content also helps performance a lot for static content!)
I second this. Also, I think the text in the database should be at least encypted by something simple like ROT13 (http://en.wikipedia.org/wiki/ROT13). In order to allow other users to use one's installation, this would at least get rid of the other user's concern that one can read the data in plain text in the database.
@tmueller78, encryption of the database would be a separate issue (but not a good approach to data privacy).
SSL is going to be as good as it gets for encryption based things at the moment, which is already possible to do. Closing.
Migrated from the original issue at https://www.assembla.com/spaces/tracks-tickets/tickets/682
Does Tracks support encryption at present? If not, are the any unofficial hacks that people who need it resort to, such as using a different HTTP server, and are there plans to implement it?
I reckon it'd be a pretty important feature; I wouldn't want the entire world to be able to sniff my traffic and learn what I'm up to.
Originally reported by Anonymous on March 3, 2008 at 02:20:57 (-0700)