Re: [CMake] Storing and auto-decrypting sensitive files in cmake SAFELY and SANELY

On 18/06/07, Gavin Beatty <[EMAIL PROTECTED]> wrote: The problem stems from storing configs in a git repository. Here, all files are either chmoded 0655 or 0755 meaning anyone knowing where to look can find my wpa2 passphrase. What I would _like_ is for ordinary user gavin (who owns the repositor

Re: [CMake] Storing and auto-decrypting sensitive files in cmake SAFELY and SANELY

Gavin Beatty wrote: Hello, Apologies if this is silly/misplaced/misguided. I'd like a way to automate decrypting (via gpg) a file, installing the decrypted form and removing the temporary decrypted file from the cmake dir. I have tried: MACRO(ETC_WPA_INSTALL src) EXEC_PROGRAM(gpg

[CMake] Storing and auto-decrypting sensitive files in cmake SAFELY and SANELY

Hello, Apologies if this is silly/misplaced/misguided. I'd like a way to automate decrypting (via gpg) a file, installing the decrypted form and removing the temporary decrypted file from the cmake dir. I have tried: MACRO(ETC_WPA_INSTALL src) EXEC_PROGRAM(gpg ARGS-o