[Owasp-esapi-c++] Base32 encoding

[Daniel Amodio]

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
Base32...
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.

-----Original Message-----
From: owasp-esapi-c++-bounces at lists.owasp.org
[mailto:owasp-esapi-c++-bounces at lists.owasp.org] On Behalf Of Da Co
Sent: Monday, August 22, 2011 1:33 PM
To: owasp-esapi-c++ at lists.owasp.org
Subject: [Owasp-esapi-c++] Base32 encoding

All,
I believe Base32 encoding should be considered as one of OWASP encodings
together with Base64, and Hexa. Base32 offers the best "cost"/"customer
friendly format" ratio out of the three methods.
I found it to very helpful for License Keys (also suggessted by Jeff
Walton in one of his code project article, Thanks, Jeff!) and UI tageted
encrypted or checksum items.
I did some POC and I could not make crypto++ 5.6 base32 talked to
commonly provided Java Base32 APIs. It seems they use different RFC.
 I was able to make a C++ implementation based on RFC3548 compatible
with Java.

Let me know if there is interest in this approach.

Regards,
daneluta
_______________________________________________
Owasp-esapi-c++ mailing list
Owasp-esapi-c++ at lists.owasp.org
https://lists.owasp.org/mailman/listinfo/owasp-esapi-c++