Dear Maintainer,

mosh upstream supports agent forwarding with --enable-agent-forwarding option.

It is enabled on arch as a separate mosh-agent package that conflicts with mosh
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=mosh-agent

Either enabling it by default or providing another package with this enabled
works.

SSH agent forwarding is a commonly requested feature for mosh.

Thank you for the suggestion!

This seems to be a fork of mosh upstream that adds out-of-band "reliable
byte streams" to the client-server protocol (based on Timo Rinne's patches
from 2012-2013, https://github.com/mobile-shell/mosh/issues/120).

Mosh upstream (https://mosh.org) doesn't have this protocol addition; the
developers aren't eager to complicate (and forever support) the protocol in
this way.

If people want to do agent forwarding, Mosh has mostly encouraged people to
do it with a separate tool (guardian-agent was one of them that was more
locked-down than normal SSH agent-forwarding, but it's also possible to use
a separate SSH/autossh/et connection to carry the agent-forwarding byte
stream).

Thank you for the suggestion!

This seems to be a fork of mosh upstream that adds out-of-band "reliable
byte streams" to the client-server protocol (based on Timo Rinne's patches
from 2012-2013, https://github.com/mobile-shell/mosh/issues/120).

Mosh upstream (https://mosh.org) doesn't have this protocol addition; the
developers aren't eager to complicate (and forever support) the protocol in
this way.

If people want to do agent forwarding, Mosh has mostly encouraged people to
do it with a separate tool (guardian-agent was one of them that was more
locked-down than normal SSH agent-forwarding, but it's also possible to use
a separate SSH/autossh/et connection to carry the agent-forwarding byte
stream).