similar to: [Bug 92] Feature: -f -f, like -f, but fork() after port/display/agent open

Displaying 20 results from an estimated 30000 matches similar to: "[Bug 92] Feature: -f -f, like -f, but fork() after port/display/agent open"

2008 Jul 02
0
[Bug 92] Feature: -f -f, like -f, but fork() after port/display/agent open
https://bugzilla.mindrot.org/show_bug.cgi?id=92 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #4 from Damien Miller <djm at
2002 Feb 01
1
FEATURE: -f -f - fork after successful open of fwd port/display/agent
Background ========== "ssh -f ..." causes ssh to fork into the background when userauth successfully completes. WHAT === With this patch "ssh -f -f ..." causes ssh to fork into the background when the first forwarded port/x11 display/agent is successfully opened. WHY === This feature makes launching remote X11 apps more reliable: when ssh exits it must have exited because
2013 Dec 19
3
[Bug 2189] New: Client fails to consider hostname when matching rfwd channel opens
https://bugzilla.mindrot.org/show_bug.cgi?id=2189 Bug ID: 2189 Summary: Client fails to consider hostname when matching rfwd channel opens Product: Portable OpenSSH Version: -current Hardware: Other OS: All Status: NEW Severity: minor Priority: P5 Component: ssh
2006 Jul 11
0
[Bug 1103] New option for ssh(1) to make it failing when remote port forwarding can't be established
http://bugzilla.mindrot.org/show_bug.cgi?id=1103 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |1155 nThis| | Status|NEW |RESOLVED Resolution|
2008 Dec 24
1
Port forwarding using the client of a multiplexed connection.
I am trying to set up port forwarding using the client of a multiplexed connection, but the client is dying. The connection paramaters I am using are as follows: for the master: /usr/bin/ssh -T -n -N -o ControlMaster=yes -o ControlPath=/var/run/autossh/control-%r@%h-%p.sock -o ConnectionAttempts=3 -o BatchMode=yes -o EscapeChar=none -o ExitOnForwardFailure=yes -o ServerAliveInterval=15 -o
2008 Aug 13
0
ProxyCommand and ExitOnForwardFailure = leftover process
Hi, I'm having a small problem when using ProxyCommand and ExitOnForwardFailure in combination with OpenSSH 5.1 under Ubuntu 8.04. In order to enable multihop scp and port forwarding, I have enabled automatic public key authenticated tunneling from hostA to hostC via hostB using ProxyCommand in my private .ssh/config file on hostA. <end of .ssh/config>: host hostB user X hostC
2015 Aug 17
6
[Bug 2444] New: ExitOnForwardFailure=yes has no effect
https://bugzilla.mindrot.org/show_bug.cgi?id=2444 Bug ID: 2444 Summary: ExitOnForwardFailure=yes has no effect Product: Portable OpenSSH Version: 6.9p1 Hardware: amd64 OS: Linux Status: NEW Severity: major Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org
2019 May 31
9
[Bug 3017] New: ExitOnForwardFailure=yes doesn't work for local forwards (-L)
https://bugzilla.mindrot.org/show_bug.cgi?id=3017 Bug ID: 3017 Summary: ExitOnForwardFailure=yes doesn't work for local forwards (-L) Product: Portable OpenSSH Version: 7.6p1 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 Component: ssh
2014 Jul 15
8
[Bug 2255] New: tunneling with -W does not report non 0 exit codes on failure even with ExitOnForwardFailure=yes
https://bugzilla.mindrot.org/show_bug.cgi?id=2255 Bug ID: 2255 Summary: tunneling with -W does not report non 0 exit codes on failure even with ExitOnForwardFailure=yes Product: Portable OpenSSH Version: 6.6p1 Hardware: amd64 OS: Linux Status: NEW Severity: normal Priority:
2016 Jul 22
2
SSH crash on OpenBSD (pledge related?)
Hello, I just ran upon this problem and couldn't find it in bugzilla. SSH crashes (abort trap) if all of the following conditions are met: (a) option -f is used (crash happens when going to background), (b) reverse port forwarding is set up (option -R), (c) option ExitOnForwardFailure is enabled, (d) there are no actual port-forwarding failures. The problem can be reproduced by
2005 Jun 21
0
[Bug 1004] X11 forwarding not working with ssh3.9p1 (Error: Can't open display)
http://bugzilla.mindrot.org/show_bug.cgi?id=1004 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From djm at mindrot.org 2005-06-21
2012 Aug 01
0
[LLVMdev] Idempotent Code Generation in LLVM
As part of PhD research I integrated support for code generation of idempotent (re-executable) code regions into LLVM, along with a supporting IR-level analysis to identify and demarcate large "semantically" idempotent regions [1]. Some have expressed interest the code, so here is a link that contains some documentation and pointers to the source hosted on GitHub:
2006 Sep 27
1
ExitOnForwardFailure and Protocol 2.0
I'm merging my "streamlocal" unix domain socket forwarding patch into 4.4p1 (or rather 20060926 SNAP) and I gather that the ExitOnForwardFailure capability only works for protocol 1.0. Am I misreading things? I was really looking forward to that feature. I noticed when I began fixing a merge reject in channel_request_remote_forwarding(). - Bill
2016 Aug 01
0
Announce: OpenSSH 7.3 released
OpenSSH 7.3 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol 2.0 implementation and includes sftp client and server support. OpenSSH also includes transitional support for the legacy SSH 1.3 and 1.5 protocols that may be enabled at compile-time. Once again, we would like to thank the OpenSSH community
2017 Jun 16
2
[PATCH] allow relative path in streamlocal forwarding
When forwarding a Unix-domain socket, the remote socket path must be absolute (otherwise the forwarding fails later). However, guessing absolute path on the remote end is sometimes not straightforward, because the file system location may vary for many reasons, including the system installation, the choices of NFS mount points, or the remote user ID. To allow ssh clients to request remote socket
2018 Nov 07
0
[PATCH v3 2/5] drm/dp_mst: Start tracking per-port VCPI allocations
On Wed, 2018-11-07 at 21:59 +0100, Daniel Vetter wrote: > On Tue, Nov 06, 2018 at 08:21:14PM -0500, Lyude Paul wrote: > > There has been a TODO waiting for quite a long time in > > drm_dp_mst_topology.c: > > > > /* We cannot rely on port->vcpi.num_slots to update > > * topology_state->avail_slots as the port may not exist if the parent > > *
2015 Aug 12
1
OT: bareos (F/OSS fork of bacula)
I'm trying to get this up and running, and have run into something that isn't clear in the docs: volumes are part of pools, I get, but I see that the limit to the number of volumes is 100. Is this a drop-dead can't-go-beyond? If I have > 100 clients to back up, do they all go to one volume, or to individual volumes? mark
2019 Jan 09
0
[PATCH v5 18/20] drm/dp_mst: Start tracking per-port VCPI allocations
There has been a TODO waiting for quite a long time in drm_dp_mst_topology.c: /* We cannot rely on port->vcpi.num_slots to update * topology_state->avail_slots as the port may not exist if the parent * branch device was unplugged. This should be fixed by tracking * per-port slot allocation in drm_dp_mst_topology_state instead of * depending on the caller to tell us how many slots
2009 Nov 04
0
[LLVMdev] idempotence
The LLVM projects page says this: "We need some way to reason about errno. Consider a loop like this: for () x += sqrt(loopinvariant);" and: "The hard part of this project is figuring out how to describe errno in the optimizer" The important property here is the idempotence of sqrt(): it is potentially side-effecting, but that side effect is independent of the
2015 Jun 29
0
Old and new package version numbers during RPM update
On 29/06/15 01:07, Kahlil Hodgson wrote: > On 29 June 2015 at 07:37, John R Pierce <pierce at hogranch.com> wrote: > >> so a regex looking for "system:" vs "system {" should nicely delineate >> these. I dunno, I might even put that into the conversion utility and >> have it just quit if the file is already in the new format, and always run