Archive
2012 (1) January (1) Ruby 1.9.3 support and new loaders 2011 (1) January (1) Loaders for Linux ARM added! 2010 (4) September (1) RubyEncoder 1.3 released June (1) RubyEncoder Teams up with Japanese Company, Soft Agency. February (1) Our Blog Update Notification January (1) Loaders Update 2009 (4) October (1) Ruby Encoder used in US Department of Defence Project March (1) Update of RubyEncoder February (1) Loaders fixed for better Ruby-Enterprise support January (1) Loaders Update 2008 (5) November (2) RubyEncoder for Windows is launched! RubyEncoder 1.1 September (1) Launch Day - RubyEncoder 1.0 August (1) We're in beta! July (1) Ruby Encoder - The First version
RubyEncoder News
Welcome to the RubyEncoder news. We'll keep you up to date with our latest developments and we have some exciting plans in the pipelineUpdate of RubyEncoder
This release includes update of the encoder and loaders. In this release:
- Encoder: added Windows Vista support
- Encoder: fixed the problem with encoded files detection containing a shell prefix #!
- Loaders: added support for Ruby 1.9.1
- Loaders: other minor fixes
The update of the encoder is recommended to users running Windows Vista. The update of loaders is recommended to users running Ruby 1.9.1.
Alex
Posted on: March 18th 2009 on 07:43am
0 Comments
Labels: 1.9.1, loaders, update, vista
Loaders Update
We have released an update for RubyEncoder Loaders. This version of loaders includes the following fixes:
- Fixed random segfault errors in loaders caused by the ruby garbage collector
- Fixed problems running protected rails configuration scripts (see below)
- Added support for Ruby-enterprise 1.8.6
Note: It is possible to encode and deploy rails configuration files usually stored in /config folder. You cannot encode *.yml database configuration script as it's not a ruby script. We suggest to use a cipher to encrypt this and load and decrypt it from the RubyEncoder protected code. So you will keep the key safe within the RubyProtected script.
Also you cannot have encoded /config/environments/*.rb scripts. Leave them unencoded. The reason for it is Rails internals. Rails loads the environment file dynamically and evaluates it with eval(). This will not work for protected scripts.
Updated loaders are available from our site http://rubyencoder.com/loaders.html
Posted on: January 29th 2009 on 05:15pm
0 Comments
Labels: loaders

