| 1 | = The encryption utility = |
| 2 | |
| 3 | The program lib/crypt_prog performs various encryption tasks. |
| 4 | |
| 5 | crypt_prog is built by the standard build procedure on Unix systems. You can also build it on Windows (with Visual Studio 2003) using the project file win_build/crypt_prog.vcproj. |
| 6 | |
| 7 | Creating encryption keys crypt_prog -genkey n private_keyfile public_keyfile Create a key pair with n bits (always use 1024). Write the keys in encoded ASCII form to the indicated files. The following commands generate the file upload and code signing key pairs. BOINC_KEY_DIR is the directory where the keys will be stored. The code signing private key should be stored only on a highly secure (e.g., a disconnected, physically secure) host. |
| 8 | {{{ |
| 9 | crypt_prog -genkey 1024 BOINC_KEY_DIR/upload_private BOINC_KEY_DIR/upload_public |
| 10 | crypt_prog -genkey 1024 BOINC_KEY_DIR/code_sign_private BOINC_KEY_DIR/code_sign_public |
| 11 | }}} |
| 12 | Or, in the test/ directory, run |
| 13 | {{{ |
| 14 | gen_keys.php |
| 15 | }}} |
| 16 | Generating signatures |
| 17 | |
| 18 | crypt_prog -sign file private_keyfile Create a digital signature for the given file. Write it in encoded ASCII to stdout. crypt_prog -sign_string string private_keyfile Create a digital signature for the given string. Write it in encoded ASCII to stdout. crypt_prog -verify file signature_file public_keyfile Verify a signature for the given file. crypt_prog -test_crypt private_keyfile public_keyfile Perform an internal test, checking that encryption followed by decryption works. |