Comments on: Bad things done well: accepting dangerous input with Rails http://info-architects.net/2008/04/02/bad-things-done-well-accepting-dangerous-input-with-rails/ Toby Hede's Blog on Ruby, Rails, Facebook Development, User Experience and Stuff Wed, 20 Aug 2008 15:31:08 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: admin http://info-architects.net/2008/04/02/bad-things-done-well-accepting-dangerous-input-with-rails/comment-page-1/#comment-128 admin Sun, 06 Apr 2008 10:06:37 +0000 http://info-architects.net/?p=79#comment-128 LiquidMarkup looks pretty comprehensive, I might have a look at it. LiquidMarkup looks pretty comprehensive, I might have a look at it.

]]> By: Web 2.0 Announcer http://info-architects.net/2008/04/02/bad-things-done-well-accepting-dangerous-input-with-rails/comment-page-1/#comment-127 Web 2.0 Announcer Sun, 06 Apr 2008 09:31:43 +0000 http://info-architects.net/?p=79#comment-127 <strong>Bad things done well: accepting dangerous input with Rails...</strong> [...]Sometimes you have to do things that are dangerous. In my case I had to accept script input from the browser and work out a way of executing it without having my system totally hacked. Discover how to run Ruby code in a Sandbox![...]... Bad things done well: accepting dangerous input with Rails…

[...]Sometimes you have to do things that are dangerous. In my case I had to accept script input from the browser and work out a way of executing it without having my system totally hacked. Discover how to run Ruby code in a Sandbox![...]…

]]>