Displaying 20 results from an estimated 6000 matches similar to: "ad-hoc ssh agent + control persist"
2011 Oct 13
1
[PATCH] Fix control persist and stdio forward interaction
As reported earlier at
https://lists.mindrot.org/pipermail/openssh-unix-dev/2011-March/029441.html
there is some strange interaction between ControlPersist and ssh -W that
breaks things if you're using both. Specifically, ssh -W host:port with
ControlPersist enabled opens up two connections to host:port and sends
data from both back.
I think this is happening because
2011 Mar 14
2
Problemes with ControlPersist
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hello,
There seems to be just a bit to do with the latest openssh (5.8p1) and
ControlPersist. I encountered two problems:
1. When I use ControlPersist in combination with ProxyCommand to reach a
other host over that proxy I get the following message:
Bad packet length 1397966893.
Disconnecting: Paket corrupt
When I fist ssh to
2023 Jul 19
9
[Bug 3589] New: ControlMaster auto, persist and -f fail.
https://bugzilla.mindrot.org/show_bug.cgi?id=3589
Bug ID: 3589
Summary: ControlMaster auto, persist and -f fail.
Product: Portable OpenSSH
Version: 9.3p1
Hardware: amd64
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: ssh
Assignee: unassigned-bugs at mindrot.org
2016 Jul 07
2
portable sftp oddity: sftp, redirection of stderr and ControPersist
hi,
Ran into a problem which I thought was an AIXism, but have since found
that it can be reproduced on Linux and MacOS. It can NOT be reproduced
on OpenBSD.
Reproduced on:
AIXv7.1 OpenSSH v6.0p1
RedHat 6.8 OpenSSH 5.4p1
Redhat 7.2 OpenSSH 6.6.1p1
MacOS 10.11 (sorry, forgot to grab the OpenSSH version)
Could not reproduce on:
OpenBSD 5.9-current, march snapshot, OpenSSH_7.2
OpenBSD
2024 Jan 06
14
[Bug 3649] New: Control sockets do not connect anymore (after updating OpenSSH)
https://bugzilla.mindrot.org/show_bug.cgi?id=3649
Bug ID: 3649
Summary: Control sockets do not connect anymore (after updating
OpenSSH)
Product: Portable OpenSSH
Version: 9.6p1
Hardware: ARM
OS: Mac OS X
Status: NEW
Severity: enhancement
Priority: P5
Component: ssh
2007 Jan 29
1
ControlPersist and multiple X11 forwarding.
Good afternoon!
I've been looking for a way to avoid having to keep my "master" ssh
session open while I have others open. This is particularly a pain
when my "master" is an scp connection.
After searching the archives, I came up with this thread
"ControlPersist and multiple X11 forwardings." However, I can't find
anything saying that it was
2007 Jul 05
36
[Bug 1330] New: RFE: 'ControlPersist' support -- automatically fork and leave ControlMaster behind as a dæmon
http://bugzilla.mindrot.org/show_bug.cgi?id=1330
Summary: RFE: 'ControlPersist' support -- automatically fork and
leave ControlMaster behind as a d?mon
Product: Portable OpenSSH
Version: 4.6p1
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component:
2011 Oct 16
4
[Bug 1943] New: [PATCH] ssh -W opens two connections when ControlPersist is enabled.
https://bugzilla.mindrot.org/show_bug.cgi?id=1943
Bug #: 1943
Summary: [PATCH] ssh -W opens two connections when
ControlPersist is enabled.
Classification: Unclassified
Product: Portable OpenSSH
Version: 5.9p1
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority:
2014 Jun 12
1
Improve ControlPersist documentation
Hi,
While testing the ControlPersist option (which is very useful by the way,
thank you), I find out that setting it to 0 has the same behaviour as
setting it to yes, while I would have expected to exit as soon as the last
client exits.
I'd like to make this behaviour clear, I think it should be documentated in
the man page for example like this:
$ cvs diff -u ssh_config.5
Index:
2007 Jul 10
1
[Bug 1338] New: Idletimeout for both client and server
http://bugzilla.mindrot.org/show_bug.cgi?id=1338
Summary: Idletimeout for both client and server
Product: Portable OpenSSH
Version: 4.6p1
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: ssh
AssignedTo: bitbucket at mindrot.org
ReportedBy: wmertens at
2015 Jul 03
6
[Bug 2420] New: Race condition regarding ControlPersist and ControlMaster=auto
https://bugzilla.mindrot.org/show_bug.cgi?id=2420
Bug ID: 2420
Summary: Race condition regarding ControlPersist and
ControlMaster=auto
Product: Portable OpenSSH
Version: 6.6p1
Hardware: amd64
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: ssh
[Bug 1917] New: Escape sequence (~) doesn't work right with ControlMaster/ControlPersist connections
2011 Jul 04
10
[Bug 1917] New: Escape sequence (~) doesn't work right with ControlMaster/ControlPersist connections
https://bugzilla.mindrot.org/show_bug.cgi?id=1917
Bug #: 1917
Summary: Escape sequence (~) doesn't work right with
ControlMaster/ControlPersist connections
Classification: Unclassified
Product: Portable OpenSSH
Version: 5.8p1
Platform: All
OS/Version: All
Status: NEW
Severity: normal
2010 Aug 16
4
Final(?) changes committed
Hi,
In addition to the strptime change that Darren has just committed to
fix Irix, I have committed a change to ssh(1) that affects all platforms:
> - djm at cvs.openbsd.org 2010/08/12 21:49:44
> [ssh.c]
> close any extra file descriptors inherited from parent at start and
> reopen stdin/stdout to /dev/null when forking for ControlPersist.
>
> prevents tools that
2020 Jan 20
4
Security implications of using ControlMaster
Dear Mailing List
We are using a ControlMaster with a short ControlPersist to access the
bastion host which then gives access to customer hosts.
Our Information Security Manager would like to disallow the
ControlMaster. His attack scenario is an admin workstation with a
compromised root account. An attacker can then use the ControlMaster to
trivially get shell access on the bastion host
2013 Jun 06
5
[Bug 1917] Escape sequence (~) doesn't work right with ControlMaster/ControlPersist connections
https://bugzilla.mindrot.org/show_bug.cgi?id=1917
Darren Tucker <dtucker at zip.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dtucker at zip.com.au
--- Comment #10 from Darren Tucker <dtucker at zip.com.au> ---
Created attachment
2011 Feb 07
1
[PATCH] ssh: set proctitle for mux master
Preserving the command line from the invoking ssh command doesn't
make much sense, so use setproctitle() to hide the arguments.
---
ssh.c | 20 +++++++++++++++++---
1 files changed, 17 insertions(+), 3 deletions(-)
diff --git a/ssh.c b/ssh.c
index d32ef78..8ebcc88 100644
--- a/ssh.c
+++ b/ssh.c
@@ -230,12 +230,25 @@ main(int ac, char **av)
struct servent *sp;
Forward fwd;
- /* Ensure
2011 Aug 25
1
Add missing -o options in ssh(1) manual
A few options appear to be missing from the list in ssh's manual.
The one I didn't add is EnableSSHKeysign, whose description implies
it is only effective when placed in the system-wide config file.
Index: ssh.1
===================================================================
RCS file: /cvs/src/usr.bin/ssh/ssh.1,v
retrieving revision 1.319
diff -u -p -r1.319 ssh.1
--- ssh.1 7 May 2011
2011 Sep 19
2
[Bug 1938] New: EscapeChar sometimes don't work when using ControlMaster
https://bugzilla.mindrot.org/show_bug.cgi?id=1938
Bug #: 1938
Summary: EscapeChar sometimes don't work when using
ControlMaster
Classification: Unclassified
Product: Portable OpenSSH
Version: 5.8p1
Platform: ix86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
2012 Apr 25
4
[Bug 2000] New: when using ssh with ControlMaster/ControlPersist, one may get zombie processes
https://bugzilla.mindrot.org/show_bug.cgi?id=2000
Bug #: 2000
Summary: when using ssh with ControlMaster/ControlPersist, one
may get zombie processes
Classification: Unclassified
Product: Portable OpenSSH
Version: 5.9p1
Platform: All
OS/Version: All
Status: NEW
Severity: major
2009 May 04
2
Multiplex tests fail on 5.2p1
I noticed "make tests" for openssh-5.2p1 fails the multiplex.sh tests.
Turns out this is because I happen to have some non-standard configuration
options in $HOME/.ssh/config and most of the multiplex.sh tests do not use
a "-F $OBJ/ssh_config" option, which means they end up reading the users
$HOME/.ssh/config.
Is this on purpose or a bug?