Lancaster-University
/
DEMOS2
Archived
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Fork for adding functionality to DĒMOS 2 needed for independent auditing.
This repository has been archived on 2022-08-01. You can view files and clone it, but cannot push or open issues or pull requests.
55 Commits 1 Branch 0 Tags 1.2 MiB
HTML 41.1%
Python 32.5%
JavaScript 25.1%
CSS 1.2%
Go to file
Ben Goldsworthy c16ac87a98 Added fork source 2022-08-01 15:04:50 +00:00
Node Committing 2018-09-11 08:31:47 +01:00
allauthdemo ajg 2018-09-19 08:38:50 +01:00
static ajg 2018-09-19 08:38:50 +01:00
.gitignore General housekeeping such as adding package.json for Node server, bash script for launching a celery worker and updating the readme to assist with launching the DEMOS2 app. Updated some models to include UI helper functions. Main work done is around event preparation - with a Celery worker running and the Node server, trustees are now emailed a link to prepare events. The event detail page has also had a bit of an overhaul to include additional information and to make it easier to use 2018-07-02 10:06:05 +01:00
LICENSE Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently 2018-06-12 13:31:38 +01:00
Makefile Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently 2018-06-12 13:31:38 +01:00
README.md Added fork source 2022-08-01 15:04:50 +00:00
commands.txt Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently 2018-06-12 13:31:38 +01:00
configure.py Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently 2018-06-12 13:31:38 +01:00
demos_cpp Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently 2018-06-12 13:31:38 +01:00
demos_cpp_bak Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently 2018-06-12 13:31:38 +01:00
manage.py Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently 2018-06-12 13:31:38 +01:00
requirements.txt Updated polls/models to include a field for storing the ballot selected by the user on the front end. A few bugs have been fixed on the event voting page and new functionality has been added which allows a voter to restart the voting process. 2018-08-22 17:39:41 +01:00
start_celery_worker.sh General housekeeping such as adding package.json for Node server, bash script for launching a celery worker and updating the readme to assist with launching the DEMOS2 app. Updated some models to include UI helper functions. Main work done is around event preparation - with a Celery worker running and the Node server, trustees are now emailed a link to prepare events. The event detail page has also had a bit of an overhaul to include additional information and to make it easier to use 2018-07-02 10:06:05 +01:00

README.md

Forked from GitHub:vincentmdealmeida/DEMOS2

DEMOS2

Prototype Django-based e-voting application, to demonstrate DEMOS2's client-side encryption e-voting.

The previous repository for DEMOS2 by Carey Williams can be found at: https://github.com/CareyJWilliams/DEMOS2

Setup

Main Application Dependencies

  • Python
    • Version 2.7; anything higher than this will not currently work
    • All Python packages specified in requirements.txt; PyCharm will detect these dependencies and offer installation
  • MySQL Server: Community Edition
    • Initialise with 'legacy password authentication'
    • Create a new MySQL DB user with the default username and password specified in aullauthdemo/settings.py
    • Create a new MySQL DB called demos2 (also specified in aullauthdemo/settings.py), making sure to set the charset to 'UTF8'

Database setup

After installing the above dependencies, issue the following command to initialise the DB:

python manage.py migrate

The first run will produce a django.db.utils.IntegrityError: (1215, 'Cannot add foreign key constraint') error. Issue the command a second time and it will complete successfully.

Settings

allauthdemo/settings.py specifies the Google reCAPTCHA site key and private key, which will need changing when deployed onto a new domain. There is also a DOMAIN setting within the file that needs updating during deployment as things like email functionality depend on this setting for correct URL generation during event preparation etc.

Emails from the application are currently sent from the following email account which can be updated within the settings:

demos2.no.reply@gmail.com

NodeJS Dependencies

The Node.js crypto server depends on the milagro-crypto-js and express modules. A package.json file can be found in the Node/ directory with these dependency requirements and therefore from this folder you can run:

npm install

Once the dependencies have been installed, you can then run the node server as per the below instructions.

Instructions

Step 1: Running the Python app and creating a new user account

You can run the server with the following command:

python manage.py runserver

The application will then be available at 127.0.0.1:8000.

You can then click on 'Join' to create a new user account.

Step 2: Running the Node.js Server

The Node.js server exposes a lot of cryptographic operations that the application depends on throughout. To run the server, issue the following command line request from the Node/ folder:

node index.js

Step 3: Running Celery

Celery is used to run tasks asynchronously and the DEMOS2 application can't run without this application. A bash script called start_celery_worker.sh is provided to make starting a worker as easy as possible:

./start_celery_worker.sh