Changes between Version 1 and Version 2 of ProofOfOwnership


Ignore:
Timestamp:
Feb 11, 2019, 6:24:04 PM (5 years ago)
Author:
Richard
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProofOfOwnership

    v1 v2  
    1 Proof of Account Ownership
     1= Proof of Account Ownership =
     2Provides your users a proof of BOINC project account ownership using OpenSSL public key cryptography. The user enters a message and that is signed alongside their account ID using the project's private key, proving that the user owns the account to external systems.
     3
     4== User guide ==
     51. Login then navigate to the 'Proof of Account Ownership' page.[[BR]]2. Enter the message you wish to be signed.[[BR]]3. Complete the captcha then submit the form.[[BR]]4. A text box will appear, copy the contents.
     6
     7== Project administrator guide ==
     8Changes required to integrate this functionality:
     9
     101. Have the latest stable OpenSSL installed on your BOINC web server.[[BR]]2. Install the latest  BOINC PR2965 web server changes:
     11
     12{{{
     13html/inc/util.inc - fixing ttok warnings
     14html/user/get_project_config.php - export public key safely
     15html/inc/user.inc - add link to account ownership form within the profile
     16
     17html/user/account_ownership_action.php - new file
     18html/user/account_ownership_form.php - new file
     19}}}
     203. Configure reCAPTCHA for the form.[[BR]]4. Generate OpenSSL keys in the /project/keys/ folder:
     21
     22{{{
     23openssl genpkey -algorithm RSA -out ownership_sign_private.pem -pkeyopt rsa_keygen_bits:2048
     24openssl rsa -pubout -in ownership_sign_private.pem -out ownership_sign_public.pem
     25}}}
     265. Adjust key permissions:
     27
     28{{{
     29chown -R boincadm:boincadm ownership_sign_p*
     30chmod --reference upload_private ownership_sign_public.pem
     31chmod --reference upload_private ownership_sign_private.pem
     32}}}
     336. Try the form, sign a message, attempt to verify the message using your public key and the decoded base64 message from the form.
     34
     35== Security ==
     36The private key needs to remain on the web server, however if this key is compromised then proof of account ownership could be forged. It's important to maintain an updated and secure BOINC project web server to reduce the risk of this happening.
     37
     38If you believe that the private key has been compromised, then simply generate a new key pair to start from scratch, users will need to regenerate their signed messages.