From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] kdialog and Chromium
Date: Tue, 31 Jul 2012 21:28:49 +0200 [thread overview]
Message-ID: <20120731192849.GD17454@siphos.be> (raw)
In-Reply-To: <5018308B.4040008@tresys.com>
On Tue, Jul 31, 2012 at 03:22:51PM -0400, Christopher J. PeBenito wrote:
> > I'm actually more inclined (and am trying to) support a downloads type where
> > browsers have the necessary rights to, but nowhere else. Browsers are a too
> > public attack vector lately so the less I need it to write (or even read)
> > user home content the better.
>
> I can go for that solution too... like a mozilla_downloads_t, user_downloads_t, or similar.
I'm currently looking at the XDG patch I mentioned a while back. The XDG
standard defines some user-related locations (Downloads, Videos, Pictures)
which I currently have labeled xdg_downloads_home_t (etc.) and marked as
customizable (btw, took me a while to realise it is sufficient to just add
"# customizable" after the type declaration to do so) so that users can mark
it easily themselves.
My XDG definitions:
~$ cat ~/.config/user-dirs.dirs
XDG_DESKTOP_DIR="$HOME/Desktop"
XDG_DOWNLOAD_DIR="$HOME/Downloads"
XDG_TEMPLATES_DIR="$HOME/"
XDG_PUBLICSHARE_DIR="$HOME/Public"
XDG_DOCUMENTS_DIR="$HOME/Documents"
XDG_MUSIC_DIR="$HOME/Music"
XDG_PICTURES_DIR="$HOME/Pictures"
XDG_VIDEOS_DIR="$HOME/Videos"
Hence, xdg_downloads_home_t, xdg_videos_home_t, xdg_pictures_home_t and
xdg_music_home_t. Don't immediately see a need for the other ones though.
Wkr,
Sven Vermeulen
next prev parent reply other threads:[~2012-07-31 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 6:14 [refpolicy] kdialog and Chromium Russell Coker
2012-07-27 9:12 ` Sven Vermeulen
2012-07-31 18:32 ` Christopher J. PeBenito
2012-07-31 19:13 ` Sven Vermeulen
2012-07-31 19:22 ` Christopher J. PeBenito
2012-07-31 19:28 ` Sven Vermeulen [this message]
2012-07-31 22:59 ` Dominick Grift
2012-07-31 23:20 ` Dominick Grift
[not found] ` <CAPzO=NwtZ3C1+t5L-byURbdxyXuq6Pb3-4EZWw6eVArkCe8qhw@mail.gmail.com>
2012-08-01 6:47 ` Sven Vermeulen
2012-08-01 14:41 ` Dominick Grift
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=20120731192849.GD17454@siphos.be \
--to=sven.vermeulen@siphos.be \
--cc=refpolicy@oss.tresys.com \
/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.