Skip to content

gaspar-ilom/crypt-cloud

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

78 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

CryptCloud

Author: [Valentin Franck] gaspar_ilom@campus.tu-berlin.de

This is just a proof of concept and should not be used in production for a number of reasons.

  • The client application contains an unaudited implementation of a cryptographic protocol (SMP) and secret keys are not stored securely in general (i.e. they are stored as a file in the application folders instead of using the OS' keyring for example. This is particularly problematic because the server acts as the CA in a PKI.).
  • TLS 1.2 is switched on by default, but it uses hard-coded self-signed certificates. One can use generate_tls_certificate.py to generate a new self-signed (unencrypted!) TLS private key and certificate (usable for localhost and crypt-cloud.com) and copy them to the correct directories in the Client and Server:
python generate_tls_certificate.py
mv tls_private_key.pem Server/tls_private_key.pem
cp tls_server_certificate.pem Client/Configuration/tls_server_certificate.pem
mv tls_server_certificate.pem Server/tls_server_certificate.pem

CryptCloud Server

Most settings for the server application can be changed in the main module 'app.py'. In particular this means the database URI, debug mode (which is set to True and must be set to False in production), the secret key, the password salt and the CA's private key passphrase in 'pki.py'. The server stores all data in a database. By default this is a Mysql database, named "flaskserver", user "flask-server", password "test123", run at localhost. These values can be changed in 'app.py'. The root certificate will be created after the first request and stored as 'CA.pem' in the application directory. It should be copied to the client (see below).

Prerequisites:

  • Python 3.5.2 (only Python version tested on Ubuntu 16.04)

  • Flask (0.12.2)

  • Flask-RESTful (0.3.6)

  • Flask-Security (3.0.0)

  • Flask-SQLAlchemy (2.3.2)

  • Werkzeug (0.14.1)

  • WTForms (2.1)

  • cryptography (2.1.4)

  • mysqlclient (1.3.12)

Install Requirements

Note that some of the prerequisites have dependencies of their own. So it is the easiest way to use pip:

pip install cryptography flask flask_security flask_sqlalchemy flask_restful mysqlclient

Launch Server application

python app.py

CryptCloud Client

The client stores most of its configuration in the 'Configuration' subfolder. In 'Configuration/settings.py' the host and port of the server can be specified. By default it loads the CA's root certificate from 'Configuration/CA.pem'. (Note this certificate is created automatically, when the server is first launched and the Client makes a request (just launch it once). It should be copied to the Client's 'Configuration'-folder.) Once the client has registered it will store its private key, the corresponding certificate issued by the CA, its secure passphrase and its credentials in the respective files in plaintext in the 'Configuration'-folder. (Yet another reason not to use this in production. Never.) The client can recover its private key and certificate from the server. This is useful to add a new device to an existing account. (For that purpose the private key is stored encrypted with a secure twelve random word passphrase.) The client allows to mutually verify other users' certificates in a synchronous SMP-session (requires a weak natural language word as a shared secret) or by scanning QR-Codes from another user's device (requires a physical meeting). Data encryption is hybrid, i.e. for each file uploaded to the server an AES-256-CBC key is generated to encrypt the data. This key is then encrypted with all users private keys, which allows easy and secure sharing! The client provides a rudimentary gui, and will write some logs to stdout.

Prerequisites:

Install Requirements

Note that some of the prerequisites have dependencies of their own. So it is the easiest way to use pip:

pip install cryptography easygui beautifulsoup4 bs4 zbar-py numpy opencv-python Pillow qrcode requests urllib3

Launch Server application

python app.py

Known Issues

  • No display of camera image, when reading QR-Codes from camera: opencv/opencv-python#46
  • Unfortunately easygui does not handle threads well. So, regarding the gui the user will only be informed of Notifications after each interaction with the Main Menu. (There is a button to retrieve and act on new notifications in the main menu.) However, a new notification will be written immediately to stdout to inform the user.

LICENSE

This code is free for anyone to to use, study, share and modify.

About

BA Thesis - Proof of Concept

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published