Re: Storing an "OAuth consumer secret" -- MIDRANGE-L

Subject: Re: Storing an "OAuth consumer secret"
From: James Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Date: Thu, 15 Dec 2011 13:01:05 -0800
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.