Specifically; on a client of mine I run

ssh USER@HOST -t perl -E SOME-CODE-HERE

and this connects to the given host as the given user, and runs the code. The code contains a little injected program that just basically pipes to a local UNIX socket, which is where my server program really runs. But that part is not too essential.

What I'm using ssh for here is
* Secrecy
* Authentication
* User-addressing
* Application-addressing

(2/3)

After 5 years of not being able to find any suitable replacement for this, I am coming to the conclusion that I will have to make it. Which upsets and annoys me because I would have thought someone else had by now. But anyway.

I'm therefore starting to think about things like names for whatever I make, and bits and pieces of technology to use to create it.

Suggestions welcome. (3/3)

Aha I think I already have a cute name. Mobility Aware Secure Transport. MAST.

mast USER@HOST APPNAME other args here...

would basically be a drop-in replacement for ssh. Now just to work out how to implement the damn thing. But since we have a name that's the easy part, right? ;)

@leonerd quic has this property. I was hoping someone would run ssh over quic. Ive experimented a few times myself but generally quic hasn't been ready yet.

However I recently noticed some people building a thing they call ssh3 which does ssh over quic. They however don't advertise it as having ip mobility. But maybe it does and they don't mention it?