search for: tiocsctty

Don't know why it works, but it works ... Rich.

...t set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell Also ^C etc does not work. Removing this ioctl call fixes this. I noticed the problem because supermin's init compiled with dietlibc worked, since the dietlibc header files don't define TIOCSCTTY and hence the ioctl was not called. --- init/init.c | 4 ---- 1 file changed, 4 deletions(-) diff --git a/init/init.c b/init/init.c index e6fd0e6..aa6c25f 100644 --- a/init/init.c +++ b/init/init.c @@ -240,10 +240,6 @@ main () /* Make current process the controlling process of the tty. */...

...found one instance of someone describing it on the net with no follow-up. I just installed openssh (3.6p1) on a linux system (running an old 2.0.34 kernel) with privilege separation disabled and get the following messages in /var/log/messages: Apr 2 15:48:34 ernestine sshd[6153]: error: ioctl(TIOCSCTTY): Operation not permitted Apr 2 15:48:34 ernestine sshd[6153]: error: open /dev/tty failed - could not set controlling tty: Device not configured The effect is that ^Z's are mostly ignored (but not by vi) and ^C kills the session, rather than a running program. After poking around the net an...

...with glibc 2.1.1) it works fine, but on another (linux kernel 2.2.20 with glibc 2.0.7) I get this in the syslog every time I log in: sshd[12277]: Accepted publickey for root from 212.38.67.158 port 2397 ssh2 PAM_pwdb[12277]: (sshd) session opened for user root by (uid=0) sshd[12280]: error: ioctl(TIOCSCTTY): Operation not permitted sshd[12280]: error: open /dev/tty failed - could not set controlling tty: Device not configured But the real issue (and this might be related to the stuff in the log?) is the behaviour of the INTR key. ssty -a says that intr has the "usual" mapping to ^C. But...

...sses can have ttyp2 be its controlling tty is if Joe invokes a setuid-Fred program explicitly from his own session. What this means is that when you make a tty your controlling tty, that tty effectively becomes yours until you''re done with it. Why not build chowning into this process? On TIOCSCTTY, the tty would chown itself to the effective uid of the current process and chmod itself to 620. Then, on close, the tty would chown itself back to root and chmod itself to 666. If the effective uid of the process opening the tty is 0, and the process is intending to start a non-root session, said...

http://bugzilla.mindrot.org/show_bug.cgi?id=536 Summary: no access to tty on Linux 2.0 Product: Portable OpenSSH Version: 3.6p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: jfeise at

...uest shell reply 0^M debug1: session_by_channel: session 0 channel 0^M debug1: session_input_channel_req: session 0 req shell^M debug1: fd 4 setting TCP_NODELAY^M debug1: channel 0: rfd 10 isatty^M debug1: fd 10 setting O_NONBLOCK^M debug2: fd 9 is O_NONBLOCK^M debug1: Setting controlling tty using TIOCSCTTY.^M Connection closed by remote host.^M debug1: channel_free: channel 0: server-session, nchannels 2^M debug3: channel_free: status: The following connections are open:^M #0 server-session (t4 r0 i0/43 o0/0 fd 10/9)^M ^M debug3: channel_close_fds: channel 0: r 10 w 9 e -1^M debug1: channel_free: c...

...chowning Newsgroups: mail.linux.kernel In-Reply-To: <199709261901.PAA04763@dcl.MIT.EDU> Organization: Cc: Bcc: "Theodore Y. Ts''o" <tytso@MIT.EDU> writes: > David Holland <dholland@eecs.harvard.edu> writes: > } Why not build chowning into this process? On TIOCSCTTY, the tty would > } chown itself to the effective uid of the current process and chmod > } itself to 620. Then, on close, the tty would chown itself back to > } root and chmod itself to 666. > >It''s a not a bad idea, but it''s not clear it meets your goal of not >r...

...l: session 0 channel 0 debug1: session_input_channel_req: session 0 channel 0 request shell reply 1 debug1: PAM setting tty to "/dev/pts/4" debug1: PAM establishing creds debug1: fd 7 setting O_NONBLOCK debug1: fd 3 IS O_NONBLOCK debug2: callback done debug1: Setting controlling tty using TIOCSCTTY. debug2: channel 0: rcvd adjust 315 ???debug1: Received SIGCHLD.??? debug1: session_by_pid: pid 4903 debug1: session_exit_message: session 0 channel 0 pid 4903 debug1: session_exit_message: release channel 0 debug1: channel 0: write failed debug1: channel 0: output open -> closed debug1: channel...

...akes a lot of explaining. I can certainly live with this one... it's the others that worry me.) I attempted some basic diagnostics myself. When I run sshd with the "-d" option and connect to it, it looks like this: debug1: Allocating pty. debug1: Setting controlling tty using TIOCSCTTY.debug1: Entering interactive session. debug1: fd 3 setting O_NONBLOCK debug1: fd 8 IS O_NONBLOCK debug1: server_init_dispatch_13 debug1: server_init_dispatch_15 ioctl(TIOCSCTTY): Invalid argument When I logout of the session: debug1: Received SIGCHLD. When I kill the ssh client:...

...ing unsupported tty mode opcode 74 (0x4a) debug1: Ignoring unsupported tty mode opcode 75 (0x4b) debug1: Received request for X11 forwarding with auth spoofing. socket: Protocol not supported debug1: Entering interactive session. debug1: fd 5 setting O_NONBLOCK debug1: Setting controlling tty using TIOCSCTTY. debug1: fd 9 IS O_NONBLOCK debug1: server_init_dispatch_13 debug1: server_init_dispatch_15 debug1: Received SIGCHLD. debug1: End of interactive session; stdin 0, stdout (read 712, sent 712), stderr 0 bytes. debug1: compress outgoing: raw data 761, compressed 526, factor 0.69 debug1: compress incom...

...debug1: server_input_channel_req: channel 0 request shell reply 0 debug1: session_by_channel: session 0 channel 0 debug1: session_input_channel_req: session 0 req shell debug1: PAM: setting PAM_TTY to "/dev/pts/1" debug1: PAM: establishing credentials debug1: Setting controlling tty using TIOCSCTTY. debug1: Received SIGCHLD. debug1: session_by_pid: pid 17636 debug1: session_exit_message: session 0 channel 0 pid 17636 debug1: session_exit_message: release channel 0 debug1: session_close: session 0 pid 17636 debug1: session_pty_cleanup: session 0 release /dev/pts/1 debug1: channel 0: free: serv...

does anyone else see this on linux: localhost sshd[14418]: Accepted password for stevesk from 15.126.45.158 port 49594 localhost sshd[14418]: Setting tty modes failed: Invalid argument redhat with kernel 2.2.17. ttymodes.c: /* Set the new modes for the terminal. */ if (tcsetattr(fd, TCSANOW, &tio) < 0) log("Setting tty modes failed: %.100s", strerror(errno)); return;

...won't work in the initramfs because no controlling console has been setup yet (I think init is the first program to do so). So, I was wondering if it might be a good idea to provide a tool in klibc (say "console_sanity") which does the console magic that sysvinit normally does (like TIOCSCTTY and tcsetattr)? Potientially it could be expanded in the future to also support loading keymaps and other bonus stuff like setting the console in utf-8 mode... It should benefit any initramfs-included shell as well since a working /dev/tty means that job control and key combinations like ctrl-c wi...

...client and host1=server But sftp immediately closes the connection in the other direction! In the error case there appear additional messages related to pseudoterminals and a SIGCHILD-event is reported on the server. Sorry, I'm not very familiar with pseudo-terminals. I've only read that TIOCSCTTY might require special access rights (CAP_SYS_ADMIN). So maybe there a some Security-related modern Linux-configurations required for sftp, which I've not been able to find. Attached please find terminal dbg-messages in the error-case (host1=sftp-client,host2=server) and the ok-case (host2...

v1 -> v2: - If we split out the init program into a separate init/ directory, that makes it much easier to build against an alternate libc. I tried to build against uClibc, but uClibc requires an entire build chain, which looked like it was going to be a massive ballache. Rich.

...ths to DSA and RSA keys too 20001112 - (bal) SCO Patch to add needed libraries for configure.in. Patch by Phillips Porch <root at theporch.com> - (bal) IRIX patch to adding Job Limits. Patch by Denis Parker <dcp at sgi.com> - (stevesk) pty.c: HP-UX 10 and 11 don't define TIOCSCTTY. Add error() to failed ioctl(TIOCSCTTY) call. 20001111 - (djm) Added /etc/primes for kex DH group neg, fixup Makefile.in and packaging files - (djm) Fix new Makefile.in warnings - (djm) Fix vsprintf("%h") in bsd-snprintf.c, short int va_args are promoted to type int. Report...

....... Starting session: shell on pts/0 for engadmin from 192.168.254.45 port 51222 id 0 debug2: fd 4 setting TCP_NODELAY debug3: set_sock_tos: set socket 4 IP_TOS 0x48 debug2: channel 0: rfd 11 isatty debug2: fd 11 setting O_NONBLOCK debug3: fd 9 is O_NONBLOCK debug1: Setting controlling tty using TIOCSCTTY. debug3: send packet: type 99 channel_output_poll_input_open: channel 0: send data: error in libcrypto debug1: do_cleanup debug3: PAM: sshpam_thread_cleanup entering debug3: mm_request_receive: entering debug3: mm_request_receive: monitor fd closed debug1: mm_reap: preauth child exited with status...

...256 debug3: tty_parse_modes: ospeed 38400 debug3: tty_parse_modes: ispeed 38400 debug1: server_input_channel_req: channel 0 request shell reply 1 debug1: session_by_channel: session 0 channel 0 debug1: session_input_channel_req: session 0 req shell debug1: Setting controlling tty using TIOCSCTTY. debug2: fd 3 setting TCP_NODELAY debug2: channel 0: rfd 8 isatty debug2: fd 8 setting O_NONBLOCK debug3: fd 6 is O_NONBLOCK debug1: Received SIGCHLD. debug1: session_by_pid: pid 6942 debug1: session_exit_message: session 0 channel 0 pid 6942 debug2: channel 0: request exit-status c...

I've reproduced this bug in versions openssh-3.7p1 and openssh-3.8p1 I've verfived that it works PERFECTLY in versions openssh-3.6p1 and openssh-2.9p2 I have not tested any other versions. The problem is sshd will not authenticate passwords off a NT4 domain using winbind and pam. Broken Debug output is: debug1: PAM: initializing for "user" debug1: PAM: setting PAM_RHOST to