This repository holds templates and encrypted credentials used by ElectronPass as well as configure.py script for compiling the templates.
When using APIs provided by online services such as Google Drive, Mega, Dropbox, programs usually have to identify themselves using a ID and SECRET. As the name suggests, at least SECRET has to be kept secret. Publishing it in the source code therefore is not an option. For retrieving your own credentials, refer to retrieving credentials.
Each app (desktop, Android, iOS ...) uses a special file which provides those variables to the compiler. Compiler then embeds them into binaries in the compile time. Why compile time? Well, if there were a configuration file containing all those variables embedded in each package, it would be quite an easy job to find it. Making it part of the binary makes it at least a bit harder, but avoiding embedding this info into our program completely is unfortunately not possible. If you somehow manage to retrieve this information from binaries, please tell us how, so we can improve ElectronPass (possibly using some obfuscation techniques).
Keys are filled into files using simple Python script, which decrypts file with keys and enters them in corresponding places in selected file. Use @KEY_NAME@ placeholder, where key needs to be entered. See this C++ example.
When keys need to be filled in, call this python script:
python3 configure.py [file_to_decrypt] [encryption_pass] [output_file]
Where [output_file] is file where you want keys to be filled in.
sample.json is a file providing sample keys. To set it as input file in configure.py you have to encrypt it first. Decrypt and encrypt files using GPG like this:
- encryption:
gpg ---smetric --cipher-algo AES256 --armor -o [output_file] [input_file] - decryption:
gpg -d -o [output_file] [input_file]
Currently, all of our apps are built using Travis CI. Such Travis configuration for desktop app is available here. To put it simple, Travis downloads and builds all the dependencies. Then it clones this repository and runs configure.py, specifying the password set in a Travis control panel (so only Travis and project admins know it). configure.py replaces the sample keys file in project sources with the right one and builds the app.
- all of the code is open source, except for the keys which can't be,
- builds can easily be automated,
- anyone can fill in his personal keys and deploy any app without having to touch the code,
- all keys are kept in one place, which makes it easy to add new keys or edit the old ones.
- this approach is quite complex and might seem like using a cannon to kill flies and
- it involves publishing encrypted content into public GitHub repositories which might be problematic? (I didn't find any good related article.)
Encryption in this repository could be done using git-crypt to make it easier for users and developers to use it.
Binaries containing the secret information could be processed using some obfuscation techniques to make retrieving this data harder.
Code in this project is licensed under GNU GPLv3 license.