MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » December 2011

Re: Storing an "OAuth consumer secret"



fixed

Raul A. Jager W. wrote:
edtf /qsys.lib/mylib.lib/myspace.usrspc'

You better encript it, a simple obfuscation may do, unless the source is easily accesible.

It's looking like the source won't be leaving the building.

We have a proprietary encryption algorithm for generating authorization codes, but it's really not suited for this.

Given that a "consumer secret" is on the order of 24 printable ASCII characters, can somebody point me to, say, "Qc3EncryptData for Dummies"?

--
JHHL





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact