From: selinux770@tortenboxer.de
To: selinux@tycho.nsa.gov
Subject: Re: wrong magic number (using old sources)
Date: Sat, 11 Aug 2007 20:07:30 +0200 [thread overview]
Message-ID: <20070811180730.308640@gmx.net> (raw)
In-Reply-To: <20070810141236.128070@gmx.net>
Hello again,
unfortunately, the problem persists. I've compiled the current stable package and put the files on the target syste... the error is still "wrong magic number"...
I also recompiled the kernel... btw... is this necessary each time i change the SELinux libraries versions? I did that too many times the last week ;-)
I've got to confess it was just a quick shot, maybe i forgot something, but I don't think so. I'll retry it on monday once a again, but I'm not very confident.
Is there some non-SELinux related library that may be responsible for this error? How is the magic number generated? How is it checked? Is some calculation or transformation performed on this number by other libraries? Since I cross-compile all the packages it may be the case that some libraries differ on the compiling system and the using system. It would be helpful to have a list to check these packages/libraries against inconsistencies that may be responsible for that....
-------- Original-Nachricht --------
Datum: Fri, 10 Aug 2007 16:12:36 +0200
Von: selinux770@tortenboxer.de
An: selinux@tycho.nsa.gov
CC: Stephen Smalley <sds@tycho.nsa.gov>
Betreff: Re: wrong magic number (using old sources)
> > > Then i think it's
> > > selinux-policy-default_1.26-7 or
> > > selinux-policy-default_1.26
> > >
> > > I'm not really sure about that, because the policy was not written by
> > me. It's only for testing. If the version of the policy is relevant,
> this
> > might by the most probable error. Which version has the policyto be (at
> least)
> > to work with the (old) packages I mentioned?
> >
> > That should be fine; you'd only run into problems if using newer
> > reference policy versions with that older checkpolicy.
> >
> > I'd suggest sending me a copy of your policy.conf and policy.20
> > off-list, and ideally giving me the precise URLs where I can find
> > the .tar.gz files that you used as your baseline. Then I can try to
> > re-create the bug.
>
> Ok, I just tried to compile the up-to-date stable package from the nsa
> page. Compiling seems to work with the help you provided. Thanks again for
> that.
>
> I will now try to bring the system up now with the new packages. This
> might take some days. I'll notify you about results.
> --
> Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
> Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
>
> --
> 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.
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
--
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:[~2007-08-11 18:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 10:10 wrong magic number (using old sources) selinux770
2007-08-10 11:45 ` Stephen Smalley
2007-08-10 11:55 ` Stephen Smalley
2007-08-10 12:12 ` selinux770
2007-08-10 12:21 ` Stephen Smalley
2007-08-10 13:07 ` "Björn Vogel"
2007-08-10 13:19 ` Stephen Smalley
2007-08-10 14:12 ` selinux770
2007-08-11 18:07 ` selinux770 [this message]
2007-08-13 12:55 ` Stephen Smalley
2007-08-15 15:44 ` selinux770
2007-08-15 18:33 ` Stephen Smalley
2007-08-16 8:05 ` selinux770
2007-08-16 12:59 ` Stephen Smalley
2007-08-16 15:14 ` selinux770
2007-08-21 17:05 ` [patch] libsepol: eliminate unaligned accesses (Was: Re: wrong magic number (using old sources)) Stephen Smalley
2007-08-21 19:21 ` Eric Paris
2007-08-21 19:33 ` Stephen Smalley
2007-08-23 15:08 ` 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=20070811180730.308640@gmx.net \
--to=selinux770@tortenboxer.de \
--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.