Re: unsafe printk
From: Pavel Machek (pavel_at_ucw.cz)
Date: 10/17/03
- Previous message: Hans Reiser: "Re: Blockbusting news, this is important (Re: Why are bad disk sectors numbered strangely, and what happens to them?)"
- In reply to: Albert Cahalan: "unsafe printk"
- Next in thread: Albert Cahalan: "Re: unsafe printk"
- Reply: Albert Cahalan: "Re: unsafe printk"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 17 Oct 2003 11:52:41 +0200 To: Albert Cahalan <albert@users.sf.net>
Hi!
> Suppose I name an executable this:
> "\n<0>Oops: EIP=0"
>
> That comes out as a KERN_EMERG log message,
> hitting the console and maybe a pager even.
>
> There seem to be a number of places in the
> kernel that printk current->comm without
> concern for what it may contain.
>
> Escape codes and non-ASCII can make for some
> interesting log messages as well. Terminals
> may have some programmable keys or answerback
> messages. So one day root is using grep on
> the log files, and they program the answerback
> string to contain a "\r\nrm -r /\r\n"...
Or at least you can make his terminal pink ;-). Unfortunately same
problem is with userland programs; root does ps and his terminal goes
pink. Sanitizing kernel messages would be good start, but ps&friends
and ls&friends need to be sanitized, too.
Pavel
-- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Hans Reiser: "Re: Blockbusting news, this is important (Re: Why are bad disk sectors numbered strangely, and what happens to them?)"
- In reply to: Albert Cahalan: "unsafe printk"
- Next in thread: Albert Cahalan: "Re: unsafe printk"
- Reply: Albert Cahalan: "Re: unsafe printk"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
