Remote encrypted message/data/command passing (basic shell)

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Avril 2a3d9e0c3a For some reaosn, any difference between exact bytes written and read (even if they are identical, just spread over different `write` calls) causes the reading half to produce garbage? ... For ESock to work, a `write(n)` needs to be paired with a `read(n)` for identical sizes of `n`. Not using `write_all(n)`+`read_exact(n)` causes this disjoint too? (Test with `write_all(n)`+`while read(...)` produced garbage.) I have no idea what is going on here. I think there"s some disconnect with the cipher, but it"s a stream cipher, so positioning (i.e. where byte pattern `A` appears in slice `B` on the writing side, and slice `C` on the reading size) shouldn"t matter right? Clearly it seems to. This is extremely disappointing. Fortune for rsh's current commit: Future small blessing − 末小吉		3 years ago
src	For some reaosn, any difference between exact bytes written and read (even if they are identical, just spread over different `write` calls) causes the reading half to produce garbage?	3 years ago
.gitignore	Started `Message` protocol.	3 years ago
Cargo.lock	Improved error messages for `set_encrypted_read()` and `exchange()`.	3 years ago
Cargo.toml	Improved error messages for `set_encrypted_read()` and `exchange()`.	3 years ago
build.rs	Encrypt + Sign tests work.	3 years ago