Jake McGinty

Looks like `std::sync::mpsc::sync_channel` might be more fitting, since we can set some sanity bounds for memory consumption. So, for example, say we wanted to use ~50MB max memory, then we'd...

Hmm, I guess that means we can't trust the SSH_CONNECTION env variable? I think that's how mosh does it though, I wonder what's different about your situation.

It doesn't, so we'd need to make our own integration / implementation (or most ideally write a more modern protocol that has baked in support for encryption and would be...

In this case I just want it to cover my use case perfectly ;). Another newer protocol to consider, though, is QUIC.

Well, shoop in server mode already daemonizes while it's sending the file. But you're right, unless I'm mistaken I think all we need to do is have a command-line flag...

Yep, right now shoop's authentication approach is "use SSH" since it's something that sysadmins already have setup. The authentication is then carried on through NaCl's secret-key authenticated encryption (XSalsa20/Poly1305). The...

@nickma82 To be honest, I'd like to rewrite shoop using Tokio. Now that async File I/O is stable there, it's a no-brainer. Because of this wish, I haven't put a...

reopen to track https://github.com/eminence/udt-rs/issues/3

@wngr I had code similar to this - unless I'm mistaken, you can't then access the `remote_addr` in warp with this setup - it always returns `None`, which is the...

Oh wow, yeah that description was unreadable looking back - sorry about that. Hopefully the updated one is a bit more readable, thanks for looking into it.