History log of /openssh-portable/PROTOCOL.mux (Results 1 - 21 of 21)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# 92b61a38 26-Sep-2018 djm@openbsd.org

upstream: Document mux proxy mode; added by Markus in openssh-7.4

Also add a little bit of information about the overall packet format

OpenBSD-Commit-ID: bdb6f6ea8580ef96792e270cae7

upstream: Document mux proxy mode; added by Markus in openssh-7.4

Also add a little bit of information about the overall packet format

OpenBSD-Commit-ID: bdb6f6ea8580ef96792e270cae7857786ad84a95

show more ...


Revision tags: V_7_8_P1, V_7_7_P1, V_7_6_P1, V_7_5_P1, V_7_4_P1, V_7_3_P1, V_7_2_P2, V_7_2_P1, V_7_1_P2, V_7_1_P1, V_7_0_P1
# 356b61f3 16-Jul-2015 djm@openbsd.org

upstream commit

describe magic for setting up Unix domain socket fowards
via the mux channel; bz#2422 patch from Daniel Black

Upstream-ID: 943080fe3864715c423bdeb7c920bb30c4eee

upstream commit

describe magic for setting up Unix domain socket fowards
via the mux channel; bz#2422 patch from Daniel Black

Upstream-ID: 943080fe3864715c423bdeb7c920bb30c4eee861

show more ...


Revision tags: V_6_9_P1, V_6_8_P1, V_6_7_P1, V_6_6_P1, V_6_5_P1, V_6_4_P1, V_6_3_P1, V_6_2_P2, V_6_2_P1, V_6_1_P1
# 7f12157c 20-Jun-2012 Damien Miller

- djm@cvs.openbsd.org 2012/06/01 00:49:35
[PROTOCOL.mux]
correct types of port numbers (integers, not strings); bz#2004 from
bert.wesarg AT googlemail.com


Revision tags: V_6_0_P1
# 4cb855b0 22-Sep-2011 Damien Miller

- djm@cvs.openbsd.org 2011/09/09 00:44:07
[PROTOCOL.mux]
MUX_C_CLOSE_FWD includes forward type in message (though it isn't
implemented anyway)


Revision tags: V_5_9_P1
# 555f3b85 14-May-2011 Damien Miller

- djm@cvs.openbsd.org 2011/05/08 12:52:01
[PROTOCOL.mux clientloop.c clientloop.h mux.c]
improve our behaviour when TTY allocation fails: if we are in
RequestTTY=auto mode

- djm@cvs.openbsd.org 2011/05/08 12:52:01
[PROTOCOL.mux clientloop.c clientloop.h mux.c]
improve our behaviour when TTY allocation fails: if we are in
RequestTTY=auto mode (the default), then do not treat at TTY
allocation error as fatal but rather just restore the local TTY
to cooked mode and continue. This is more graceful on devices that
never allocate TTYs.

If RequestTTY is set to "yes" or "force", then failure to allocate
a TTY is fatal.

ok markus@

show more ...


# c067f625 14-May-2011 Damien Miller

- djm@cvs.openbsd.org 2011/05/06 22:20:10
[PROTOCOL.mux]
fix numbering; from bert.wesarg AT googlemail.com


# 6c3eec7a 05-May-2011 Damien Miller

- djm@cvs.openbsd.org 2011/04/17 22:42:42
[PROTOCOL.mux clientloop.c clientloop.h mux.c ssh.1 ssh.c]
allow graceful shutdown of multiplexing: request that a mux server
remo

- djm@cvs.openbsd.org 2011/04/17 22:42:42
[PROTOCOL.mux clientloop.c clientloop.h mux.c ssh.1 ssh.c]
allow graceful shutdown of multiplexing: request that a mux server
removes its listener socket and refuse future multiplexing requests;
ok markus@

show more ...


Revision tags: V_5_8_P2, V_5_8_P1
# b407dd8d 03-Feb-2011 Damien Miller

- djm@cvs.openbsd.org 2011/01/31 21:42:15
[PROTOCOL.mux]
cut'n'pasto; from bert.wesarg AT googlemail.com


Revision tags: V_5_7_P1
# 42747df8 13-Jan-2011 Damien Miller

- djm@cvs.openbsd.org 2011/01/13 21:55:25
[PROTOCOL.mux]
correct protocol names and add a couple of missing protocol number
defines; patch from bert.wesarg AT googlemail.com


Revision tags: V_5_6_P1
# 388f6fc4 21-May-2010 Damien Miller

- markus@cvs.openbsd.org 2010/05/16 12:55:51
[PROTOCOL.mux clientloop.h mux.c readconf.c readconf.h ssh.1 ssh.c]
mux support for remote forwarding with dynamic port allocation,

- markus@cvs.openbsd.org 2010/05/16 12:55:51
[PROTOCOL.mux clientloop.h mux.c readconf.c readconf.h ssh.1 ssh.c]
mux support for remote forwarding with dynamic port allocation,
use with
LPORT=`ssh -S muxsocket -R0:localhost:25 -O forward somehost`
feedback and ok djm@

show more ...


Revision tags: V_5_5_P1, V_5_4_P1
# b401f922 09-Feb-2010 Damien Miller

This should have gone in with the multiplexing merge, but I dropped it
at the time.


# 356b61f3 16-Jul-2015 djm@openbsd.org

upstream commit

describe magic for setting up Unix domain socket fowards
via the mux channel; bz#2422 patch from Daniel Black

Upstream-ID: 943080fe3864715c423bdeb7c920bb30c4eee

upstream commit

describe magic for setting up Unix domain socket fowards
via the mux channel; bz#2422 patch from Daniel Black

Upstream-ID: 943080fe3864715c423bdeb7c920bb30c4eee861

show more ...


# 7f12157c 20-Jun-2012 Damien Miller

- djm@cvs.openbsd.org 2012/06/01 00:49:35
[PROTOCOL.mux]
correct types of port numbers (integers, not strings); bz#2004 from
bert.wesarg AT googlemail.com


# 4cb855b0 22-Sep-2011 Damien Miller

- djm@cvs.openbsd.org 2011/09/09 00:44:07
[PROTOCOL.mux]
MUX_C_CLOSE_FWD includes forward type in message (though it isn't
implemented anyway)


# 555f3b85 14-May-2011 Damien Miller

- djm@cvs.openbsd.org 2011/05/08 12:52:01
[PROTOCOL.mux clientloop.c clientloop.h mux.c]
improve our behaviour when TTY allocation fails: if we are in
RequestTTY=auto mode

- djm@cvs.openbsd.org 2011/05/08 12:52:01
[PROTOCOL.mux clientloop.c clientloop.h mux.c]
improve our behaviour when TTY allocation fails: if we are in
RequestTTY=auto mode (the default), then do not treat at TTY
allocation error as fatal but rather just restore the local TTY
to cooked mode and continue. This is more graceful on devices that
never allocate TTYs.

If RequestTTY is set to "yes" or "force", then failure to allocate
a TTY is fatal.

ok markus@

show more ...


# c067f625 14-May-2011 Damien Miller

- djm@cvs.openbsd.org 2011/05/06 22:20:10
[PROTOCOL.mux]
fix numbering; from bert.wesarg AT googlemail.com


# 6c3eec7a 05-May-2011 Damien Miller

- djm@cvs.openbsd.org 2011/04/17 22:42:42
[PROTOCOL.mux clientloop.c clientloop.h mux.c ssh.1 ssh.c]
allow graceful shutdown of multiplexing: request that a mux server
remo

- djm@cvs.openbsd.org 2011/04/17 22:42:42
[PROTOCOL.mux clientloop.c clientloop.h mux.c ssh.1 ssh.c]
allow graceful shutdown of multiplexing: request that a mux server
removes its listener socket and refuse future multiplexing requests;
ok markus@

show more ...


# b407dd8d 03-Feb-2011 Damien Miller

- djm@cvs.openbsd.org 2011/01/31 21:42:15
[PROTOCOL.mux]
cut'n'pasto; from bert.wesarg AT googlemail.com


# 42747df8 13-Jan-2011 Damien Miller

- djm@cvs.openbsd.org 2011/01/13 21:55:25
[PROTOCOL.mux]
correct protocol names and add a couple of missing protocol number
defines; patch from bert.wesarg AT googlemail.com


# 388f6fc4 21-May-2010 Damien Miller

- markus@cvs.openbsd.org 2010/05/16 12:55:51
[PROTOCOL.mux clientloop.h mux.c readconf.c readconf.h ssh.1 ssh.c]
mux support for remote forwarding with dynamic port allocation,

- markus@cvs.openbsd.org 2010/05/16 12:55:51
[PROTOCOL.mux clientloop.h mux.c readconf.c readconf.h ssh.1 ssh.c]
mux support for remote forwarding with dynamic port allocation,
use with
LPORT=`ssh -S muxsocket -R0:localhost:25 -O forward somehost`
feedback and ok djm@

show more ...


# b401f922 09-Feb-2010 Damien Miller

This should have gone in with the multiplexing merge, but I dropped it
at the time.