From: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
To: russell@coker.com.au
Cc: SELinux List <selinux@tycho.nsa.gov>
Subject: Re: labeling of compilers etc
Date: Mon, 30 Jan 2006 01:26:46 +0100 [thread overview]
Message-ID: <1138580807.9012.52.camel@estila> (raw)
In-Reply-To: <200601301003.17498.russell@coker.com.au>
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
On lun, 2006-01-30 at 10:03 +1100, Russell Coker wrote:
> Limiting access to wget would also imply doing the same to lynx, links, ftp,
> ncftp, netcat, and many others.
Right.
> What do you consider to be the issues relating to tar etc?
I'm generally talking about binfmt/file parsing risks. 'tar' shouldn't
be able to do anything more than what it has been designed for.
Cheers,
--
Lorenzo Hernández García-Hierro <lorenzo@gnu.org>
[1024D/6F2B2DEC] & [2048g/9AE91A22][http://tuxedo-es.org]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-30 0:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 0:56 labeling of compilers etc Russell Coker
2006-01-29 13:33 ` Steve G
2006-01-29 18:39 ` Russell Coker
2006-01-29 22:08 ` Lorenzo Hernández García-Hierro
2006-01-29 23:03 ` Russell Coker
2006-01-30 0:26 ` Lorenzo Hernández García-Hierro [this message]
2006-01-30 5:10 ` Russell Coker
2006-01-30 14:29 ` Stephen Smalley
2006-01-31 7:47 ` Russell Coker
2006-02-01 2:34 ` Daniel J Walsh
2006-02-01 8:22 ` Russell Coker
2006-02-01 12:51 ` Daniel J Walsh
2006-02-01 23:15 ` Russell Coker
2006-02-01 13:45 ` Stephen Smalley
2006-02-01 13:47 ` Stephen Smalley
2006-02-01 23:27 ` Russell Coker
2006-02-02 12:32 ` Stephen Smalley
2006-02-03 11:15 ` Russell Coker
2006-02-03 13:26 ` Stephen Smalley
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=1138580807.9012.52.camel@estila \
--to=lorenzo@gnu.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.