| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
AWS KMS for now, work-in-progress
|
|
As pointed out in #10, the binary names are quite generic. Rename
`client` to `roughenough-client` and `server` to `roughenough-server`.
Fixes #10
|
|
|
|
Benchmarks were out-of-date copy-pasta and misleading.
|
|
Update `untrusted` dependency to fix #6. Update README.
|
|
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
|
|
|
|
|
|
|
|
Aaron1011's changes bring Roughenough to a 1.0.0 level of functionality.
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
We want to get latest patch version on build. Assumes crates
are following semver semantics and patch version changes are
non-breaking.
|
|
Fern's configurability and features are overkill. As a bonus, compile
time and binary size both shrink a bit.
|
|
As `[bench]` isn't in stable Rust yet, use [Criterion.rs]https://github.com/japaric/criterion.rs)
as the benchmarking harness.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
