Commit 18e8c7ae authored by Loïck Bonniot's avatar Loïck Bonniot

v0.2.0

parent 4ab104fc
Pipeline #956 passed with stages
CHANGELOG
=========
v0.2.0
------
> 25/04/2016
#### CLI Client
- Update command-line interface to match POSIX standards (!64)
#### GUI Client
- Add menu bar (!65)
- Add show contract screen (!65)
- Add fetch contract screen (!65)
- Add signature screen (!61)
- Add basic help message box (!66)
- Add about message box for DFSS (!66)
- Add about message box for Qt (!66)
- Add user mail and selected platform information (!66)
- Improve buttons and feedbacks (!66)
+ Buttons now use the full width of the window
+ Error messages are now displayed in message boxes
#### Platform
- Fix crash if a client disconnects before the ready signal (!60)
- Update command-line interface to match POSIX standards (!63)
#### TTP
- Update command-line interface to match POSIX standards (!64)
#### Demonstrator
- Increase arrow length to 30px (!67)
- Update default unit from nano-second to micro-second (!67)
- Update command-line interface to match POSIX standards (!64)
#### Misc
- Improve security of network communication by checking server's certificate (!62)
v0.1.0
------
> 18/04/2016
......
......@@ -40,14 +40,14 @@ You can configure several parameters for that (check the `help` command of `dfss
For instance, if we are running the plaform on the `example.com` host:
```bash
./dfssp -cn example.com -country FR -rootValidity 3650 init
./dfssp --cn example.com --country FR --validity 3650 init
```
Then, it is possible to create TTP credentials from generated root credentials.
The generated files are stored in a subdirectory "ttp".
```bash
./dfssp -cn ttp.example.com -country FR -certValidity 365 ttp
./dfssp --cn ttp.example.com --country FR --validity 365 ttp
```
You can then start the platform. Here we are considering a mongoDB database running on the same host.
......@@ -70,7 +70,7 @@ Then:
You can also start the TTP:
```bash
./dfsst -cert ttp/cert.pem -key ttp/cert.pem start
./dfsst --cert ttp/cert.pem --key ttp/cert.pem start
```
### Setup clients
......@@ -79,18 +79,18 @@ Each client needs the `dfssp_rootCA.pem` file in order to connect to the platfor
Clients can then register on the platform with the following command:
```bash
./dfssc -ca path/to/dfssp_rootCA.pem -host example.com register
./dfssc --ca path/to/dfssp_rootCA.pem --host example.com register
```
A mail will be sent to the user containing a unique token. Use this token to authenticate onto the platform:
```bash
./dfssc -ca path/to/dfssp_rootCA.pem -host example.com auth
./dfssc --ca path/to/dfssp_rootCA.pem --host example.com auth
```
When this is done, the client will have a certificate and a private key in the current directory.
It's then possible to send new contracts to the platform:
```bash
./dfssc -ca path/to/dfssp_rootCA.pem -host example.com new
./dfssc --ca path/to/dfssp_rootCA.pem --host example.com new
```
......@@ -8,7 +8,7 @@ import (
)
// Version represents the current version of the DFSS software suite
const Version = "0.2.0-dev"
const Version = "0.2.0"
// VersionCmd is the cobra command common to all dfss modules
var VersionCmd = &cobra.Command{
......
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