[email protected] (Richard Kenner) writes: > Here's a possible design: > > - There's optionally a file in the config > directory called "master_key". It contains just a string. > > - A CLI command "core encrypt <string>" is added to Asterisk. It takes the > provided string, encrypts it using the string in master_key, and outputs > a string of the form "{enc:<encrypted_version_of_string}". > > - The config file reader looks for strings of the form "{enc:<string>}: > and replaces them, before otherwise parsing the line, with the decrypted > version of the string using the key in the "master_key" file.
This sounds pretty reasonable, except perhaps that you might only want to convert strings in password fields -- otherwise you risk false positives in e.g. the dial plan. I can recommend contracting with one of the indepedent Asterisk developers to get this done. You will likely find them on the Asterisk-biz-list. /Benny -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
