Commit 7ea76c17 authored by Frauke's avatar Frauke
Browse files

Inital release

parents
# Logs
logs
*.log
# Runtime data
pids
*.pid
*.seed
# Directory for instrumented libs generated by jscoverage/JSCover
lib-cov
# Coverage directory used by tools like istanbul
coverage
# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
.grunt
# Compiled binary addons (http://nodejs.org/api/addons.html)
build/Release
# Dependency directory
# Commenting this out is preferred by some people, see
# https://www.npmjs.org/doc/misc/npm-faq.html#should-i-check-my-node_modules-folder-into-git-
node_modules
# Users Environment Variables
.lock-wscript
# IDEs and editors (shamelessly copied from @angular/cli's .gitignore)
/.idea
.project
.classpath
.c9/
*.launch
.settings/
*.sublime-workspace
# IDE - VSCode
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json
### Linux ###
*~
# temporary files which can be created if a process still has a handle open of a deleted file
.fuse_hidden*
# KDE directory preferences
.directory
# Linux trash folder which might appear on any partition or disk
.Trash-*
# .nfs files are created when an open file is removed but is still being accessed
.nfs*
### OSX ###
*.DS_Store
.AppleDouble
.LSOverride
# Icon must end with two \r
Icon
# Thumbnails
._*
# Files that might appear in the root of a volume
.DocumentRevisions-V100
.fseventsd
.Spotlight-V100
.TemporaryItems
.Trashes
.VolumeIcon.icns
.com.apple.timemachine.donotpresent
# Directories potentially created on remote AFP share
.AppleDB
.AppleDesktop
Network Trash Folder
Temporary Items
.apdisk
### Windows ###
# Windows thumbnail cache files
Thumbs.db
ehthumbs.db
ehthumbs_vista.db
# Folder config file
Desktop.ini
# Recycle Bin used on file shares
$RECYCLE.BIN/
# Windows Installer files
*.cab
*.msi
*.msm
*.msp
# Windows shortcuts
*.lnk
# Others
lib/
data/
public/js/script.js
server/files
# Libsodium Spike
Use libsodium to implement Spike 1: OpenCrypto
## About
### Goals
* Which implementations should we spike (and why?)
* libsodium.js
* js-nacl
* Natrium
* Natrium Browser
* What are the differences in workflow between Spike 1 and Spike 2? Which is easier to work with?
* What are the security implications of using a libsodium port (which gives us better ciphers) instead of the WebCrypto API (which gives us unextractable keys)? (This is a question we should post to some friendly neighbourhood cryptographers in the community.)
## Getting Started
Getting up and running is as easy as 1, 2, 3.
1. Make sure you have [NodeJS](https://nodejs.org/) **latest LTS version** and [npm](https://www.npmjs.com/) installed.
2. Install your dependencies
```
cd path/to/spike/Libsodium; npm install
```
3. Start your app
```
npm start
```
## Help
For more information on this spike visit the [Indienet documentation](https://indienet.info/spikes/security/#spike-2-re-implement-spike-1-using-libsodium)
## Notes
## Changelog
__0.1.0__
- Initial release
## License
Copyright (c) 2018 Aral Balkan, Ind.ie (Article 12)
Licensed under the [AGPLv3](LICENSE).
{
"name": "libsodium-spike",
"version": "1.0.0",
"description": "Use libsodium to implement Spike 1: OpenCrypto",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"repository": {
"type": "git",
"url": "git@source.ind.ie:indienet/spikes/security/Libsodium.git"
},
"author": "Wim Vantomme, Frauke Vanderzijpen",
"license": "ISC"
}
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment