From: Paul Krumviede <pwk@acm.org>
To: Russell Coker <russell@coker.com.au>, selinux@tycho.nsa.gov
Subject: Re: [ISN] Music file flaws could threaten traders
Date: Thu, 19 Dec 2002 14:41:27 -0800 [thread overview]
Message-ID: <18223383.1040308887@localhost> (raw)
In-Reply-To: <200212192307.20386.russell@coker.com.au>
--On Thursday, 19 December, 2002 23:07 +0100 Russell Coker
<russell@coker.com.au> wrote:
> This type of thing could affect Linux in the same way as it affects
> Windows.
i'm not so sure. the bugtraq posting about the windows XP bug
indicated that it could be exploited even without downloading
a file to the user's computer. if using explorer, the file had to be
on the local machine, but didn't need to be "played" to allow
an exploit. i don't think that either case is relevant to selinux
(but would like to know if i'm wrong).
i haven't looked at the winamp report yet.
-paul
> Currently we have "risky" programs such as netscape, games, and IRC
> clients in their own domains that have types for read-only and for
> read-write files (and no ability to run gpg or other important programs).
>
> The problem about doing the same for audio/video programs such as players
> for avi, mp3, and vob files is that their typical use involves
> downloading files from the net to play immediately so that denying them
> read access to user_home_t files will give a large decrease in
> functionality. I believe that there are two major categories of SE
> Linux users, those who will never run such A/V programs on Linux, and
> those who won't use any security software that gets in the way of their
> entertainment.
>
> So I think that having a domain for A/V programs such as $1_av_t that has
> read access to $1_home_t and can create files with the type $1_home_av_t
> may not be as tightly secured as we might like, but the people who are
> concerned about that won't use it anyway.
>
> On Thu, 19 Dec 2002 09:58, InfoSec News wrote:
>> http://news.com.com/2100-1001-978403.html?tag=fd_top
>>
>> By Robert Lemos
>> Staff Writer, CNET News.com
>> December 18, 2002, 5:12 PM PT
>>
>> A security firm on Wednesday warned that people using Windows XP or
>> popular music player WinAmp could fall prey to a vulnerability,
>> enabling a modified music file to take control of a person's PC.
>
> --
> http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
> http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
> http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
> http://www.coker.com.au/~russell/ My home page
>
>
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov
> with the words "unsubscribe selinux" without quotes as the message.
>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2002-12-19 22:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0212190257480.19905-100000@idle.curiosity.org>
2002-12-19 22:07 ` [ISN] Music file flaws could threaten traders Russell Coker
2002-12-19 22:41 ` Paul Krumviede [this message]
2002-12-20 6:45 ` Russell Coker
2002-12-20 0:16 ` Brian May
2002-12-20 7:23 ` Russell Coker
2002-12-20 23:46 ` Brian May
2002-12-21 18:20 ` Russell Coker
2002-12-20 9:15 ` Tom
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=18223383.1040308887@localhost \
--to=pwk@acm.org \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
/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.