<div dir="ltr"><div>Many of our users' requests for a "roamable ssh-agent forwarding" might already be served by running ssh-over-OpenVPN.</div><div><br></div><div>The main benefits from "slosh" would be:</div>
<div><br></div>(1) It would be runnable by an unprivileged user.<div><br></div><div>(2) It would keep TCP connections open even when sleeping and resuming later.</div><div><br></div><div>(3) It would allow roaming with no fuss (I think OpenVPN is already pretty close to this, but most VPNs aren't).</div>
<div><br></div><div>(4) It would exploit multihoming to stripe datagrams across the best set of IPv4/v6 addresses available to the server and client.</div><div><br></div><div>-Keith</div><div class="gmail_extra"><br>
<br><div class="gmail_quote">On Wed, Dec 18, 2013 at 4:11 PM, Jim Cheetham <span dir="ltr"><<a href="mailto:jim.cheetham@otago.ac.nz" target="_blank">jim.cheetham@otago.ac.nz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Excerpts from Keith Winstein's message of 2013-12-19 07:35:16 +1300:<br>
<div>> (For the future, I think we have decided not to go in this direction of<br>
> adding ssh-agent forwarding and X11 forwarding and SOCKS forwarding to Mosh<br>
> and just to make a generic "slosh" as a separate program that ferries a<br>
> reliable stream across a roaming, multihomed connection.<br>
<br>
</div>What would be the effective difference between that idea, and an actual<br>
VPN?<br>
<span><font color="#888888"><br>
-jim<br>
--<br>
Jim Cheetham, Information Security, University of Otago, Dunedin, N.Z.<br>
✉ <a href="mailto:jim.cheetham@otago.ac.nz" target="_blank">jim.cheetham@otago.ac.nz</a> ☏ <a href="tel:%2B64%203%20470%204670" value="+6434704670" target="_blank">+64 3 470 4670</a> ☏ m <a href="tel:%2B64%2021%20227%200015" value="+64212270015" target="_blank">+64 21 227 0015</a><br>
⚷ OpenPGP: B50F BE3B D49B 3A8A 9CC3 8966 9374 82CD C982 0605<br>
</font></span></blockquote></div><br></div></div>