Re: Warning, cua2 opened, ...
Alan Cox (alan@lxorguk.ukuu.org.uk)
Mon, 16 Mar 1998 08:34:56 +0000 (GMT)
- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Gert Doering: "Re: Warning, cua2 opened, ..."
- Previous message: Gert Doering: "Re: Re[2]: Warning, cua2 opened, ..."
- Next in thread: Gert Doering: "Re: Warning, cua2 opened, ..."
- Reply: Gert Doering: "Re: Warning, cua2 opened, ..."
- Reply: Theodore Y. Ts'o: "Re: Warning, cua2 opened, ..."
> to be on by default by the kernel at boot-up time --- and that wasn't an
> accident. (2) tcsetattr is one of the few ioctl's which is allowed
> after a hangup, so it will work anyway.
Ok thats the bit I needed to know. That means I can SIG_IGN sighup and
sort it.
> Yes, this is a potential security hole which a user who left a program
> running might possibly exploit, but there's little that user could do
> other than a denial of service attack, and there are plenty of ways of
That hole only exists because Linus needs to be fed the revoke() patch
again I think
> the device is directly connected, I have to ask why CLOCAL is getting
> cleared in the first place.
It may well not be. I can't guarantee what the port has been doing before
however.
Thanks a lot
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
- Next message: Gert Doering: "Re: Warning, cua2 opened, ..."
- Previous message: Gert Doering: "Re: Re[2]: Warning, cua2 opened, ..."
- Next in thread: Gert Doering: "Re: Warning, cua2 opened, ..."
- Reply: Gert Doering: "Re: Warning, cua2 opened, ..."
- Reply: Theodore Y. Ts'o: "Re: Warning, cua2 opened, ..."