Bug 24 - no controlling terminal problems
Summary: no controlling terminal problems
Status: CLOSED INVALID
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: ssh (show other bugs)
Version: -current
Hardware: All FreeBSD
: P2 normal
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-27 22:50 AEDT by halber mensch
Modified: 2004-04-14 12:24 AEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description halber mensch 2001-11-27 22:50:47 AEDT
Okay.. here's the skinny.. please refrain from killing me..

Decided to see if I could swap in a new drive and retain all the contents of 
the original filesystem.. so I used pax to copy the file system (except /proc, 
which I learned was a bad bad bad thing to copy).. eventually I got all the 
files transferred with proper permissions and owners and such. System boots 
fine and does normal services .. but..

but when any user on the machine (aside from root) tries to ssh to any host 
(even the local host), they are kicked back with an error stating there is no 
controlling terminal. I know this is no bug in ssh, but I need to know in what 
cases ssh will terminate like that. I've checked all of my tty entries in /dev 
and they all appear to be functioning normally. I'm baffled. The only thing I 
can think of is if there may be some trick permission that's been tripped. 
*shrug*
I was under the impression that ssh simply tries to write to the user's 
terminal device and craps out if there is no real terminal device or if the 
device isn't writeable.. is there anything I'm missing?
Comment 1 Markus Friedl 2001-12-11 06:59:01 AEDT
please provide debugging output from 
	ssh -v -v -v
Comment 2 Damien Miller 2002-04-17 13:06:38 AEST
Five months with no followup = no bug
Comment 3 Damien Miller 2004-04-14 12:24:17 AEST
Mass change of RESOLVED bugs to CLOSED