Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!howland.reston.ans.net!xlink.net!math.fu-berlin.de!informatik.tu-muenchen.de!hphalle2!weisss
From: weisss@Informatik.TU-Muenchen.DE (Stefan Weiss)
Subject: [???BSD] Shell keeps running after modem hangs up
Keywords: com, getty, shell, HUP, login
Sender: news@Informatik.TU-Muenchen.DE (USENET Newssystem)
Organization: Technische Universitaet Muenchen, Germany
Date: Sat, 19 Jun 1993 09:31:13 GMT
Message-ID: <weisss.740482273@hphalle2>
Lines: 37
I have the following problem with 386bds AND netbsd:
What I did:
I enabled the getty on com2. (And connected a modem to com2.)
I called the modem and got the login prompt and logged in.
I interrupted the telephone line so the modems lost carrier and
hung up.
I reconnected the line and dialed the modem again.
The modems connected and I got -- no, no login prompt -- the shell
that ran when the connection broke down. Hey! That's handy. You
needn't relogin when the connection breaks down. You can just
continue your work where you left it some seconds (or hours) ago.
Well, I guess there are some people out there who think that's
quite a security hole. (In fact the hole is so big you can walk right
through it and don't even have to take off your hat.)
What I suppose:
The bug is in the com-driver. The shell gets no hangup signal.
Didn't anyone notice this before? Or am I too blind to see an obvious
solution to this problem?
I know this problem since Version 0.1 without and with patchkits. And
even NetBSD has this feature.
A friend of mine reported this problem, too. So I don't think it's
on my hardware.
BTW: Can it be? NetBSD comes without uucp? uuuuh!
Stefan
---------------------------------------------
Stefan Weiss stw@contrib.de
Germering, Oberbayern
Germany IRC: Chagall
---------------------------------------------
Gegen Rassismus und Extremismus.
---------------------------------------------