This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Projects/Owasp Esapi Ruby"

From OWASP
Jump to: navigation, search
Line 31: Line 31:
 
| release_3 =
 
| release_3 =
 
| release_4 =
 
| release_4 =
 +
 +
<!--- The line below is for GPC usage only. Please do not edit it --->
  
 
| project_about_page = Projects/Owasp_Esapi_Ruby
 
| project_about_page = Projects/Owasp_Esapi_Ruby
 
}}
 
}}

Revision as of 18:47, 14 April 2011

PROJECT INFO
What does this OWASP project offer you? 		RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: Owasp Esapi Ruby (home page)
Purpose: The Owasp Esapi Ruby is a port for outstanding release quality Owasp Esapi project to the Ruby programming language. The idea is to build a Ruby gem (the standard ruby library archive format) containing the Esapi concepts implemented in Ruby classes so people using Ruby in their Rails application can have security into them.
License: BSD license
who is working on this project?
Project Leader(s):
Project Contributor(s):
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: Mailing List Archives
Project Roadmap: View
Main links:
Key Contacts
current release
Owasp Esapi Ruby v0.30.0 - March 2011 - (download)
Release description:
  • The OWASP Esapi Ruby gem will require at least version 1.9.2 of Ruby interpreter to make sure to have full advantages of the newer language APIs. In particular version 1.9.2 introduces radical changes in the following areas:
    • Regular expression engine (to be written)
    • UTF-8 support
    • Unicode support in 1.9.2 is much better and provides better support for character set encoding/decoding
      • All strings have an additional chunk of info attached: Encoding
      • String#size takes encoding into account – returns the encoded character count
      • You can get the raw datasize
      • Indexed access is by encoded data – characters, not bytes
      • You can change encoding by force but it doesn’t convert the data
    • Dates and Time
      • From “Programming Ruby 1.9“
      • “As of Ruby 1.9.2, the range of dates that can be represented is no longer limited by the under- lying operating system’s time representation (so there’s no year 2038 problem). As a result, the year passed to the methods gm, local, new, mktime, and utc must now include the century—a year of 90 now represents 90 and not 1990.“
Rating: Yellow button.JPG Not Reviewed - Assessment Details
last reviewed release
Not Yet Reviewed


other releases

Retrieved from "https://wiki.owasp.org/index.php?title=Projects/Owasp_Esapi_Ruby&oldid=108926"