From: Juanma Barranquero <lekktu@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Emacs and SELinux contexts
Date: Mon, 7 Jun 2010 11:58:23 +0200 [thread overview]
Message-ID: <AANLkTikqllmmEg0vCCRVdXk2ZSAIIwM5zqVQnpeLcA6V@mail.gmail.com> (raw)
In-Reply-To: <4C0C942B.8050002@gmail.com>
On Mon, Jun 7, 2010 at 08:39, Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
> I have noticed something with emacs on GNU/Linux systems. When you edit
> something with Emacs, the SELinux context of the file doesn't stay
> preserved. This could be an issue when you edit configuration or policy
> files as root. A system setting file usually has a context like this,
The etc/NEWS currently on the Emacs repository has this:
** Basic SELinux support has been added.
This requires Emacs to be linked with libselinux at build time.
*** Emacs preserves the SELinux file context when backing up, and
optionally when copying files. To this end, copy-file has an extra
optional argument, and backup-buffer and friends include the SELinux
context in their return values.
*** The new functions file-selinux-context and set-file-selinux-context
get and set the SELinux context of a file.
*** Tramp offers handlers for file-selinux-context and
set-file-selinux-context
for remote machines which support SELinux.
so (some) SELinux support will be included on 24.1. Unfortunately,
that will likely be many months from now.
If you need that support now you can try building Emacs directly from
the current development sources.
Juanma
next prev parent reply other threads:[~2010-06-07 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 6:39 Emacs and SELinux contexts Suvayu Ali
2010-06-07 9:58 ` Juanma Barranquero [this message]
2010-06-07 14:48 ` Suvayu Ali
[not found] <mailman.22.1275892792.30245.help-gnu-emacs@gnu.org>
2010-06-07 7:10 ` Glenn Morris
2010-06-07 16:27 ` Stefan Monnier
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=AANLkTikqllmmEg0vCCRVdXk2ZSAIIwM5zqVQnpeLcA6V@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=fatkasuvayu+linux@gmail.com \
--cc=help-gnu-emacs@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.