From: Giacomo Lozito <city_hunter@azzurra.org>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: cdrecord as normal user broken with kernel 2.6.8.1
Date: Sat, 28 Aug 2004 12:22:13 +0200 [thread overview]
Message-ID: <200408281222.14293.city_hunter@azzurra.org> (raw)
It's crystal clear that applications should run correctly with a kernel,
and it is not the kernel that should be made to work with them.
By the way, things are already getting fixed in next kernel releases.
Nevertheless, a problem exists.
I wouldn't expect relevant things (such as CD burning) to broke within stable
series of a kernel. It's ok if things break with 2.5 or 2.7, but should it be
the same for 2.6?
In my humble opinion, a nice and good way to tighten security for some
commands was to give it as an option in ATA/ATAPI/MFM/RLL or SCSI section in
kernel configuration.
That way people could read "this option improves security, it will become
standard in later kernels, but be aware that it could make cdrecording tools
not functional when they are run from a normal user account"
and people could decide what to do.
Wasn't that more reasonable?
Regards,
Giacomo Lozito
next reply other threads:[~2004-08-28 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 10:22 Giacomo Lozito [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-15 23:42 PROBLEM: cdrecord as normal user broken with kernel 2.6.8.1 GhePeU
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=200408281222.14293.city_hunter@azzurra.org \
--to=city_hunter@azzurra.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox