[Owasp-esapi-c++] Base32 encoding
Kevin W. Wall
kevin.w.wall at gmail.com
Thu Aug 25 10:35:09 EDT 2011
On Thu, Aug 25, 2011 at 10:14 AM, Daniel Amodio
<dan.amodio at aspectsecurity.com> wrote:
> I don't see any reason why it would be a `bad` idea to include Base32.
> Is there any reason this was left out of ESAPI Java?
> Maybe just me, but I haven't heard a lot of mainstream usage of
> Would there be a good demand for the usage if it was in there?
> Note -- It won't be that hard to spin up a Base32 Codec if the code is
> already done.
It was left of of ESAPI for JavaEE simply because Base32 encoding
is rarely, if ever, used in the Java world. (I can't recall anyone *ever* using
it in my 12+ yrs of Java experience in the enterprise.) Usually people
use Base64 encoding instead.
Given a base64 implementation, it shouldn't be very hard to hack that
to a base32 implementation, but IMO, we should only di it if there is
sufficient demand. Furthermore, in the spirit of consistency across all
ESAPI implementations, if we do this for ESAPI for C++, it ideally should
be done for the other dozen or so language implementations as well.
What's everyone's thoughts on this?
"The most likely way for the world to be destroyed, most experts agree,
is by accident. That's where we come in; we're computer professionals.
We *cause* accidents." -- Nathaniel Borenstein
More information about the Owasp-esapi-c++