summaryrefslogtreecommitdiff
path: root/Cargo.toml
AgeCommit message (Collapse)Author
2019-01-23Enhanced client stats logging outputStuart Stock
2019-01-21Initial add of simple stats collectorStuart Stock
2019-01-20Clean and refactor server's inner loopStuart Stock
2019-01-19Rust 2018 edition migrationStuart Stock
2018-12-25add a simple criterion-based benchmarkStuart Stock
2018-10-28Release 1.1.1 to correct missing aux data in AWS KMS decrypt pathStuart Stock
Auxilliary data was not provided in encryption context provided to AWS KMS decrypt() call, causing unwrapping to fail.
2018-10-14one-way GCP KMS workingStuart Stock
2018-10-07checkpointStuart Stock
2018-10-07Land KMS support, yay!Stuart Stock
AWS KMS for now, work-in-progress
2018-10-07Give client and server binaries more distinctive namesStuart Stock
As pointed out in #10, the binary names are quite generic. Rename `client` to `roughenough-client` and `server` to `roughenough-server`. Fixes #10
2018-10-07prep 1.0.5 releaseStuart Stock
2018-09-29Remove critereon based benchmarkStuart Stock
Benchmarks were out-of-date copy-pasta and misleading.
2018-07-28Release 1.0.4Stuart Stock
Update `untrusted` dependency to fix #6. Update README.
2018-07-28Update 'untrusted' to 0.6 for upstream security fixStuart Stock
Update 'untrusted' 0.5 -> 0.6 to pull in security fix in 0.6.2. https://github.com/RustSec/advisory-db/pull/24 Also update 'ring' to 0.13 to be compatible with untrusted 0.6. Fixes #6
2018-03-28Version 1.0.3Stuart Stock
2018-03-24Release 1.0.2Stuart Stock
2018-03-24Release 1.0.1Stuart Stock
2018-03-15Release 1.0.0Stuart Stock
Aaron1011's changes bring Roughenough to a 1.0.0 level of functionality.
2018-03-11Add support for batch-signing requestsAaron Hill
As documented in the Roughtime spec, servers can batch together requests, only signing the root of a computed Merkle tree, in order to increase efficiency. Following the example of the reference Roughtime implementation, the default batch size is set to 64. However, this value can be changed in the config. Two pieces of benchmark infrastructure are added - a simple "benchmark mode" on the server, and a "stress test mode" on the client. These features can be used to help pick an optimal batch size for the server. In "benchmark mode", the server does not log any requests. Instead, it prints out the current request processing speed every second. This helps to keep the output manageable when using the client's "stress test" mode. In "stress test mode", the client sends the same message to the server in a loop. To prevent accidental flooding of the users's local network, or a remote server, only loopback addresses are supported in this mode.
2018-03-10version 0.3.1Stuart Stock
2018-03-10Update README and Cargo with info on client; verison bump to 0.3.0Stuart Stock
2018-03-01Add client implementationAaron Hill
2018-02-250.2.1Stuart Stock
2018-02-240.2.0Stuart Stock
2018-02-24Don't specify patch version on several dependenciesStuart Stock
We want to get latest patch version on build. Assumes crates are following semver semantics and patch version changes are non-breaking.
2018-02-24Use simple_logger instead of fernStuart Stock
Fern's configurability and features are overkill. As a bonus, compile time and binary size both shrink a bit.
2018-02-17Add benchmarks for message and response creationStuart Stock
As `[bench]` isn't in stable Rust yet, use [Criterion.rs]https://github.com/japaric/criterion.rs) as the benchmarking harness.
2017-12-30Improve crate-level docsStuart Stock
2017-12-30Additional metadata entires for cargoStuart Stock
2017-09-23update to Ring 0.12.1 and Untrusted 0.5.1Stuart Stock
2017-07-06read from config; updated READMEStuart Stock
2017-07-05add logging and ctrl-c handlerStuart Stock
2017-07-03add docstrings and cleanup whitespaceStuart Stock
2017-06-22simplistic semi-working serverStuart Stock
2017-06-19begin work on serverStuart Stock
2017-06-17initial commitStuart Stock