From: Dale Amon <amon@vnl.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Dale Amon <amon@vnl.com>, SELinux List <SELinux@tycho.nsa.gov>
Subject: Re: More Debian bugs
Date: Fri, 23 Sep 2005 22:03:47 +0100 [thread overview]
Message-ID: <20050923210347.GB21546@vnl.com> (raw)
In-Reply-To: <1127506232.27851.100.camel@moss-spartans.epoch.ncsc.mil>
[-- Attachment #1: Type: text/plain, Size: 2468 bytes --]
On Fri, Sep 23, 2005 at 04:10:32PM -0400, Stephen Smalley wrote:
> You can change it to build policy.19 by adding the -c 19 option to
> checkpolicy. Attached policy Makefile diff from upstream CVS causes it
> to build both versions and load the right one.
Good. Still, someone should update the patches in Debian. If
they are that far behind, lord only knows what other bugs
are still in there.
> > sepol_genusers: can't find system.users
> > No such file or directory
> > unable to get boolean names: No surc file or directory
>
> That's technically ok; load_policy will fall back to just the raw binary
> policy image if those files don't exist. But the Debian policy package
> should create them nonetheless, like the Fedora one.
Okay, that should mean I'm just about there.
> > I also note there are some dangling softlinks created
> > by the setools package:
> >
> > /usr/share/setools/
> > lrwxrwxrwx 1 root root 24 2005-09-23 18:18 seaudit-report.conf -> /etc/seaudit-report.conf
> > lrwxrwxrwx 1 root root 23 2005-09-23 18:18 seaudit-report.css -> /etc/seaudit-report.css
> > lrwxrwxrwx 1 root root 16 2005-09-23 18:18 seuser.conf -> /etc/seuser.conf
> >
> > But the targets are not at those locations, they are:
> > /etc/setools/
> > -rw-r--r-- 1 root root 2805 2005-09-15 08:29 seaudit-report.conf
> > -rw-r--r-- 1 root root 3040 2005-09-15 08:29 seaudit-report.css
> > -rw-r--r-- 1 root root 1815 2005-09-15 08:29 seuser.conf
>
> Hmmm...on Fedora, they aren't symlinks and there is no /etc/setools.
> You may just want to grab the latest upstream tarball for setools from
> Tresys and build it directly. But note that setools is purely optional;
> it is not required for operation of SELinux at all.
I included these for completeness... like the other
error messages they are not fatal but are something
that the packager should fix just to be tidy.
I'll have to see if I have time to swap drives this
evening and have another go. I presume I'm on my own
over the weekend...
--
------------------------------------------------------
Artemis Systems Development
Dale Amon amon@islandone.org +44-7802-188325
International linux systems consultancy
Hardware & software system design, security
and networking, systems programming and Admin
"Have Laptop, Will Travel"
------------------------------------------------------
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-23 21:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 19:52 More Debian bugs Dale Amon
2005-09-23 20:10 ` Stephen Smalley
2005-09-23 20:24 ` Stephen Smalley
2005-09-23 21:03 ` Dale Amon [this message]
[not found] ` <20050924013709.GA27686@vnl.com>
2005-09-26 13:33 ` Dale Amon
2005-10-09 10:19 ` Russell Coker
2005-10-09 14:50 ` Luke Kenneth Casson Leighton
2005-10-09 20:44 ` Russell Coker
2005-10-09 22:08 ` Luke Kenneth Casson Leighton
2005-10-09 23:09 ` Russell Coker
2005-10-10 9:05 ` Luke Kenneth Casson Leighton
2005-10-13 4:31 ` Dale Amon
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=20050923210347.GB21546@vnl.com \
--to=amon@vnl.com \
--cc=SELinux@tycho.nsa.gov \
--cc=sds@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.