more eloquent readme

This commit is contained in:
Aidan Hahn 2019-05-23 19:40:46 -07:00
parent 18f5ffd289
commit 4cb9d3a5e1
No known key found for this signature in database
GPG key ID: 327711E983899316

View file

@ -11,10 +11,12 @@ Simply run the folllowing command:
```shell ```shell
$ ./buildwrapper.sh $ ./buildwrapper.sh
``` ```
buildwrapper will ask you for details about the client and server, if you are testing this software both CNs can be set to localhost. Buildwrapper will ask you for details about the client and server. If you are testing this software both CNs can be set to localhost.
buildwrapper will then generate CAs for the Client and Server, and signed certs for the Client and Server. IN addition a seperate, third CA and cert will be generated for testing purposes. Buildwrapper will then generate CAs for and signed certs for the Client and Server. In addition a seperate, third CA and cert will be generated for testing purposes.
Gradle will then generate protobuf source and compile it with the source for the client and server. Gradle will then generate protobuf source and compile it with the java source for the client and server.
After gradle is completed buildwrapper will organize the sources with their respective certs in the staging folder. In addition to a server folder and a client folder, there will be a test folder which has a copy of all certs and both server and client functionality. The test CA is not trusted by the server or the client by default. As such, the test cert can be used to induce a mutual tls authentication failure. After gradle is finished compiling and running the junit tests, buildwrapper will organize the sources with their respective certs in the staging folder.
In addition to a server folder and a client folder, there will be a test folder which has a copy of all certs and both server and client functionality.
The test CA is not trusted by the server or the client by default. As such, the test cert can be used to induce a mutual tls authentication failure.
# Running # Running
After build, the programs can be found in the staging folder. After build, the programs can be found in the staging folder.