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).
On Wed, May 21, 2025 at 6:09 AM Pirate Praveen <
praveen@debian.org> wrote:
Package: mosh
Version: 1.4.0-1+b2
Severity: important
X-Debbugs-Cc: praveen@debian.org
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.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.25-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mosh depends on:
ii dpkg 1.22.18
ii libc6 2.41-7
ii libgcc-s1 14.2.0-19
ii libprotobuf32t64 3.21.12-11
ii libssl3t64 3.5.0-1
ii libstdc++6 14.2.0-19
ii libtinfo6 6.5+20250216-2
ii libutempter0 1.2.1-4
ii openssh-client 1:10.0p1-2
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
Versions of packages mosh recommends:
ii perl-base [libio-socket-ip-perl] 5.40.1-3
mosh suggests no packages.
-- no debconf information
<div dir="ltr"><div>Thank you for the suggestion!</div><div><br></div><div>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, <
a href="
https://github.com/mobile-shell/mosh/issues/120" target="_blank">
https://github.com/mobile-shell/mosh/issues/120</a>).</div><div><br></div><div>Mosh upstream (<a href="
https://mosh.org" target="_blank">
https://mosh.org</a>) doesn't have this
protocol addition; the developers aren't eager to complicate (and forever support) the protocol in this way.</div><div><br></div><div>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).</div></div><br><div class="gmail_quote"><div dir="ltr"
class="gmail_attr">On Wed, May 21, 2025 at 6:09 AM Pirate Praveen <<a href="mailto:
praveen@debian.org" target="_blank">
praveen@debian.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Package: mosh<br>
Version: 1.4.0-1+b2<br>
Severity: important<br>
X-Debbugs-Cc: <a href="mailto:
praveen@debian.org" target="_blank">
praveen@debian.org</a><br>
Dear Maintainer,<br>
mosh upstream supports agent forwarding with --enable-agent-forwarding option.<br>
It is enabled on arch as a separate mosh-agent package that conflicts with mosh<br>
<a href="
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=mosh-agent" rel="noreferrer" target="_blank">
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=mosh-agent</a><br>
Either enabling it by default or providing another package with this enabled<br>
works.<br>
SSH agent forwarding is a commonly requested feature for mosh.<br>
-- System Information:<br>
Debian Release: trixie/sid<br>
APT prefers unstable<br>
APT policy: (500, 'unstable'), (1, 'experimental')<br> Architecture: amd64 (x86_64)<br>
Kernel: Linux 6.12.25-amd64 (SMP w/8 CPU threads; PREEMPT)<br>
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set<br> Shell: /bin/sh linked to /usr/bin/dash<br>
Init: systemd (via /run/systemd/system)<br>
LSM: AppArmor: enabled<br>
Versions of packages mosh depends on:<br>
ii dpkg 1.22.18<br>
ii libc6 2.41-7<br>
ii libgcc-s1 14.2.0-19<br>
ii libprotobuf32t64 3.21.12-11<br>
ii libssl3t64 3.5.0-1<br>
ii libstdc++6 14.2.0-19<br>
ii libtinfo6 6.5+20250216-2<br>
ii libutempter0 1.2.1-4<br>
ii openssh-client 1:10.0p1-2<br>
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1<br>
Versions of packages mosh recommends:<br>
ii perl-base [libio-socket-ip-perl] 5.40.1-3<br>
mosh suggests no packages.<br>
-- no debconf information<br>
</blockquote></div>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)