From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: serial port
Date: Mon, 19 Nov 2007 19:13:00 +0200 [thread overview]
Message-ID: <4741C41C.4070704@nic.fi> (raw)
In-Reply-To: <474138C6.3070508@sfu.ca>
Daryl Van Humbeck wrote:
> If you wanted to enable both serial and graphical terminals (or any
> other kind(s) of terminals, just that there are more than one enabled at
> once), you'd really have to switch to using the Model/View/Controller
> architecture for user interaction.
That has been the plan.
> However there is also the difficulty that when you have two separate
> terminals into the same session (or whatever else you want to think of),
> that might become a security issue.
That is up-to user to choose what to do. If user do not care about
security through any of the terminals then he/she can disable it (or
better not to enable it at all). Then again you can reconsider whole
security concept of the whole system if you do not trust one input.
Making system secure is quite hard job, it kinda requires total
knowledge of the system and that is not always even possible.
next prev parent reply other threads:[~2007-11-19 17:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 21:31 serial port Robert Millan
2007-11-18 11:33 ` Marco Gerards
2007-11-18 11:56 ` Robert Millan
2007-11-18 12:12 ` Vesa Jääskeläinen
2007-11-18 12:24 ` Robert Millan
2007-11-18 12:41 ` Marco Gerards
2007-11-18 12:32 ` Marco Gerards
2007-11-18 12:43 ` Vesa Jääskeläinen
2007-11-19 7:18 ` Daryl Van Humbeck
2007-11-19 17:13 ` Vesa Jääskeläinen [this message]
2007-11-18 12:14 ` Marco Gerards
-- strict thread matches above, loose matches on Subject: below --
2021-02-11 11:22 Serial Port Leandro Bucci
2021-02-11 12:52 ` Philippe Gerum
2005-02-17 7:41 serial port Tim Newsham
2005-02-18 1:36 ` Tim Newsham
2004-07-24 15:11 serial port read working but not write Jan-Benedict Glaw
2004-08-03 17:41 ` Serial port suresh shenoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4741C41C.4070704@nic.fi \
--to=chaac@nic.fi \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.