diff --git a/src/sock/enc.rs b/src/sock/enc.rs index 07ccc4d..22a108f 100644 --- a/src/sock/enc.rs +++ b/src/sock/enc.rs @@ -462,7 +462,8 @@ impl ESock } //XXX: For some reason, non-exact reads + writes cause garbage to be produced on the receiving end? -// Is this fixable? Why does it disjoint? I have no idea... This is supposed to be a stream cipher, right? Why does positioning matter? Have I misunderstood how it workd? Eh... +// Is this fixable? Why does it disjoint? I have no idea... This is supposed to be a stream cipher, right? Why does positioning matter? Have I misunderstood how it workd? Eh... +// With this bug, it seems the `while read(buffer) > 0` construct is impossible. This might make this entirely useless. Hopefully with the rigid size-based format for `Message` we won't run into this problem, but subsequent data streaming will likely be affected unless we use rigid, fixed, and (inefficiently) communicated buffer sizes. impl AsyncWrite for ESock where W: AsyncWrite