Croodle is an end-to-end encrypted web application to schedule a date or to do a poll on a any topic. All data like title, description, number and labels of options, available answers and names of users and their selections are encrypted/decrypted in the browser using strong 256-bit AES encryption.
This is an alpha version. Changes could brake backward compatibility. It is also not well tested and some features are missing. It is not meant for productive use yet.
Croodle is inspired by PrivateBin and, of course, by Doodle.
As any other web application based end-to-end encryption Croodle could be attacked by an injection of malicious code on serverside or threw a man-in-the-middle attack. If an attacker could inject for example JavaScript, they would be able to read the decrypted content in the browser or the encryption key that is used used and exfiltrate that data.
Therefore you have to:
- use an encrypted connection to the server hosting Croodle. In most use cases this will be an HTTPS connection. We strongly recomend people hosting Croodle to force an encrypted connection.
- trust the server.
Theoretically you could also check for an attack like this by analysing the source code retrieved from server and/or using developer tools of your browser and check what data is send over the network or stored in cookies, local storage or similar browser techniques.
Croodle is designed to have as few as possible requirements on the server it is running on. Croodle runs on almost every web space with PHP >= 7.2. Croodle stores the data in textfiles, so there is no need for a database server like MySQL.
Due to security reasons you should have TLS encryption enabled and provide a valid certificate. (see the security notice)
Production builds are provided as github release assets.
If you like to build yourself you have to install node, ember-cli and composer before. It's recommended using volta to ensure a compatible and tested node version is used.
git clone [email protected]:jelhan/croodle.git
cd croodle
npm install
cd api/ && composer install --no-dev && cd ..
npm run buildAfterwards copy all files in /dist folder to your werbserver.
The API can be configured by creating a config.php inside api/ folder which returns an associative array.
Have a look at api/config.default.php for available options.
data/folder has to be writeable by web server, but must not be accessible publicly. Protect it in your webserver configuration or move it out of webroot by changingdataDirapi option.- Croodle uses subresource integrity (SRI) for assets. Therefore you must not tamper with build output (e.g. you have to disable cloudflare Auto Minify feature). If that's not an option for you, you have to disable SRI and build yourself.
- HTTPS connection should be forced. You should consider using HTTP Strict Transport Security (HSTS) and HTTP Public Key Pinning (HPKP).
- Content-Security-Policy (CSP) and Referrer-Policy headers should be used. Default headers are provided in
.htaccessfile but commented out. - Execute
php api/cron.phpon a regular basis to delete outdated polls. A cronjob running once a day should be fine.
ember serve generates a development build of Croodle and starts
a server listening on http://localhost:4200 which is serving it.
If source files are changing, a rebuild and reload is triggered.
By default Croodle uses an api mock in development. Since that one does not persist records all polls are gone after a reload.
If you like to test against the real API, you should run the API using php built-in web server locally:
php -S 127.0.0.1:8080 -t dist/Afterwards start ember-cli development server using --proxy option:
ember server --proxy http://127.0.0.1:8080Ember-cli clears dist folder on each rebuild. If you like to keep created polls over rebuild, configure api to use a non default folder to save your polls:
CROODLE__DATA_DIR=/tmp/croodle_data php -S 127.0.0.1:8080 -t dist/ember test --server is the prefered way to run tests in Chrome. Results are reported in command-line and browser. Files are watched for changes.
If you like to run tests only once in a headless Chrome and Firefox execute ember test. This is also used in CI.
Additionally tests are available in all development builds. This allows you to execute the tests in any browser of your choice by running ember serve and opening http://locahost:4200/tests.
Tests are run against a mock-api provided by ember-cli-mirage. Therefor they don't cover system integration.
API tests are provided by Codeception. To run them change current
directory to /api and execute ./vendor/bin/codecept run. You have
to install composer development requirements before (composer install
without --no-dev option).
Cross-browser testing provided by
Croodle is MIT Licensed.