roughenough - A Roughtime secure time sync client and server written in Rust

Age	Commit message (Collapse)	Author
2018-10-07	wip checkpoint; nearly round-trip kms	Stuart Stock

2018-10-07	checkpoint	Stuart Stock

2018-10-07	start work on envelope encryption for long-term seed	Stuart Stock

2018-10-07	Land KMS support, yay!	Stuart Stock
	AWS KMS for now, work-in-progress
2018-10-07	Give client and server binaries more distinctive names	Stuart 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-07	prep 1.0.5 release	Stuart Stock

2018-10-02	Minor Rustdoc updates	Stuart Stock

2018-10-02	Final touches and bow-tieing on configuration. Update README to reflect.	Stuart Stock

2018-09-30	Work-in-progress; still working to clean up config	Stuart Stock

2018-09-30	Separate trait objects for file- and environment-based server config	Stuart Stock

2018-09-30	Report unknown configuration key in FileConfig	Stuart Stock

2018-09-29	Bump version in lib.rs	Stuart Stock

2018-09-29	Major refeactoring for better code structure	Stuart Stock
	* Extract distinct types for online and long-term keys * Extract and create separate configuration trait and implementation(s) * Clean-ups, renames, tidying
2018-07-28	bump version constant to 1.0.4, oops	Stuart Stock

2018-03-28	Version 1.0.3	Stuart Stock

2018-03-28	limit message tag count to 1024	Stuart Stock

2018-03-24	Release 1.0.2	Stuart Stock

2018-03-24	Fix incorrect range check in multi_tag_message()	Stuart Stock
	9656fda introduced a buggy range check when ensuring that the value's end offset does not extend past the end of the payload.
2018-03-24	Release 1.0.1	Stuart Stock

2018-03-24	Additional documentation	Stuart Stock

2018-03-24	Check single tag message length	Stuart Stock

2018-03-24	Restructure from_bytes; check length and alignment early	Stuart Stock

2018-03-24	Check that value offset does not extend pass end of message	Stuart Stock

2018-03-24	Merge branch 'fuzz' of github.com:int08h/roughenough into fuzz	Stuart Stock

2018-03-24	add docstring for from_bytes()	Stuart Stock

2018-03-20	Handle malformed message with truncated tag bytes	Stuart Stock

2018-03-20	Validate offsets do not point beyond end of message	Stuart Stock

2018-03-20	Reject messages with zero tags	Stuart Stock

2018-03-18	Return Error on invalid offset instead of panic'ing	Stuart Stock

2018-03-17	Apply default rustfmt style to the project.	Stuart Stock

2018-03-15	Missed updating lib.rs version constant to 1.0.0	Stuart Stock

2018-03-15	Merge pull request #3 from Aaron1011/batch_final	Stuart Stock
	Add support for batch-signing requests
2018-03-12	Cleanly handle receive errors from socket	Aaron Hill

2018-03-12	Use an Arc to share response counter	Aaron Hill

2018-03-12	Update docs to include client	Stuart Stock

2018-03-12	Fix merkle tests	Aaron Hill

2018-03-12	Remove unecessary flat_map	Aaron Hill
	This gives another ~50,000 reqs/second on my machine
2018-03-12	Only sign SREP once per batch	Aaron Hill

2018-03-11	Update documentation for new batch_size option	Aaron Hill

2018-03-11	Add support for batch-signing requests	Aaron 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-10	version 0.3.1	Stuart Stock

2018-03-10	Read server socket until `WouldBlock`	Stuart Stock
	Using the `-n` feature of @Aaron1011's excellent client I was able to find and fix a nagging bug. Post conversion from the hand-rolled event loop to a `mio` based one, the server would intermittently fail to respond to client requests. The server's UDP socket is edge-triggered and the `mio` docs clearly state that [operations must be performed until `WouldBlock`](https://carllerche.github.io/mio/mio/struct.Poll.html#edge-triggered-and-level-triggered) otherwise `poll` might not return subsequent events. Fix is to loop inside the MESSAGE token match until `recv_from` returns `WouldBlock`. The resulting code is excessively nested; a cleanup will follow.
2018-03-10	Correct a Missed conversion to hex::encode	Stuart Stock

2018-03-10	Additional changes on top of client contribution in #1	Stuart Stock

2018-03-10	Merge pull request #1 from Aaron1011/final_client	Stuart Stock
	Add client implementation
2018-03-10	Use a consistent version constant for server and client	Stuart Stock

2018-03-10	Convert to use of hex crate (https://crates.io/crates/hex)	Stuart Stock
	As part of landing #1, make existing server and test code consistent with client by using hex crate instead of forked copy of 'hex.rs'.
2018-03-10	Log bytes retured from send_to() and the nonce prefix when responding	Stuart Stock

2018-03-01	Add client implementation	Aaron Hill

2018-02-25	Initialize logger at INFO level	Stuart Stock
	Artifact of switching from fern. Init logging at INFO so mio's timeout TRACE statements do not spam the log.