Displaying 7 results from an estimated 7 matches for "request_tty".
2015 Feb 20
3
SUCCESS: OpenSSH_6.7p1-snap20150220
Compiled OK, and operating nicely on CentOS 6.6, both 32/64 bit.
Really appreciate the UpdateHostkeys feature!
One issue I noticed, the screen output gets garbled if the user has been "asked" to "Accept" the new hostkeys.
Looks like the screen output is missing the CR's, and only LF's get presented.
[root at be2 .ssh]# ssh be1 ls -l
Warning: Permanently added
2013 Jun 20
1
ProxyCommand that returns a socket
Hello,
My usage of ProxyCommand just calls the nc utility with various
parameters. That in turn after the initial setup just copies copies
the data from the network socket to stdin/stdout. This useless coping
can be avoided if ssh has an option to receive the socket from the
proxy command. I suppose it can improve network error reporting as ssh
would talk directly to the network socket rather
2012 Apr 01
0
[Bug 1995] New: RequestTTY=no in config doesn't work if stdin is not a tty
...uch activity). So this time I'm
writing more proper bug report using bugzilla.
I've noticed that RequestTTY option added in 8bf1740144a4 (May 2011) is
not working 100% as intended (unless used in command-line). I checked
the source code and it's because some tty stuff (touching
options.request_tty) is performed before reading config file.
I think that init log output, read per-user config, fill defaults and
log reinit should be put just after buffer_init(...).
Such fix has been tested and it seems to be working fine, but I may
overlooked some (corner) cases, so please look at my solution in...
2016 May 31
7
[Bug 2577] New: Port Forwarding on Proxy with ProxyCommand ssh -W does not work / bad file descriptor
https://bugzilla.mindrot.org/show_bug.cgi?id=2577
Bug ID: 2577
Summary: Port Forwarding on Proxy with ProxyCommand ssh -W does
not work / bad file descriptor
Product: Portable OpenSSH
Version: 7.2p1
Hardware: amd64
OS: Linux
Status: NEW
Severity: major
Priority: P5
2013 Oct 07
4
Feature request: FQDN Host match
Hello!
I'm hoping that Gmail won't HTML format this mail so that I'll get flamed :)
Anyway, my question relates to ssh_config. The problem I find is that
the Host pattern is only applied to the argument given on the command
line, as outlined in the man page:
"The host is the hostname argument given on the command line (i.e. the
name is not converted to a canonicalized host name
2012 Dec 21
0
File Attachments for previous bug report
...);
- bzero(gc, sizeof(*gc));
+ memset(gc, 0, sizeof(*gc));
xfree(gc);
}
@@ -867,7 +867,7 @@
int cancel_port, ok;
Forward fwd;
- bzero(&fwd, sizeof(fwd));
+ memset(&fwd, 0, sizeof(fwd));
fwd.listen_host = fwd.connect_host = NULL;
leave_raw_mode(options.request_tty == REQUEST_TTY_FORCE);
-------------- next part --------------
--- hostfile.c.orig 2012-12-19 17:19:15.393667218 -0800
+++ hostfile.c 2012-12-19 17:19:50.752556571 -0800
@@ -330,7 +330,7 @@
xfree(hostkeys->entries[i].host);
xfree(hostkeys->entries[i].file);
key_free(hostkeys->entr...
2012 Dec 20
4
Deprecated calls to bzero() and index() found in OpenSSH 6.1p1
...emset(gc, 0, sizeof(*gc));
xfree(gc);
}
@@ -867,7 +867,7 @@
int cancel_port, ok;
Forward fwd;
- bzero(&fwd, sizeof(fwd));
+ memset(&fwd, 0, sizeof(fwd));
fwd.listen_host = fwd.connect_host = NULL;
leave_raw_mode(options.request_tty == REQUEST_TTY_FORCE);
In file 'hostfile.c', I've replaced the bzero() call with
the equivalent memset() call. The patch file is below in
(diff -u) format:
--- hostfile.c.orig 2012-12-19 17:19:15.393667218 -0800
+++ hostfile.c 2012-12-19 17:19:50.752556571 -0800
@@ -330,7 +330,7...