From: Lorenzo Hernandez Garcia-Hierro <lorenzo@gnu.org>
To: selinux@tycho.nsa.gov
Cc: linux-kernel@vger.kernel.org
Subject: SELinux port for 2.4.28 (and incoming backport from 2.6) released.
Date: Sat, 04 Dec 2004 21:38:43 +0100 [thread overview]
Message-ID: <1102192723.19001.19.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
Hi,
I was wondering for a backport of SELinux patch for the 2.4 brand, and
i've observed that there's just a patch, deprecated, for 2.4.26.
As the first move for trying to backport the current 2.6 patch
capabilities i've ported the old 2.4.26 patch to 2.4.28, without huge
problems and just fixing some errors with proc fs stuff and others.
I've not tested it yet, but hopefully works.
I want to know if someone is interested in doing this, as the main
reasons are that 2.4 kernels are used by many people, possibly more than
the ones using revisions from the 2.6 brand, and also that we can offer
the possibility of using the SELinux enhancements without changing the
kernel.In addition, if you compare 2.6 revisions changelogs with 2.4
ones you can see that many things change between releases, and not in
2.4 that are only security related and critical or major enhancements.
The gzip'ed patch can be found at:
https://sourceforge.net/project/showfiles.php?group_id=118309&package_id=137453
Joshua was telling me that many things changed in the 2.6 releases, and
that many things are deprecated or obsolete in the old 2.4.26 patch, so,
i will appreciate any help for backporting them and giving support for
those new capabilities.
I'm CC'ing the LKML because this could be of interest for the kernel
hackers, in an hypothetical case of including a backported and updated
version of SELinux patch in the 2.4 brand.
Cheers and enjoy,
PS: I'm not an experienced developer in C terms, i just do what i can do
and often i get obsessed when i can't get something done, so, i think
that equilibrates the balance of knowledge<->attitudes (it's not easy to
fit all of this in time when you're just fifteen years old, but i can't
excuse unexpected kernel panics :) ).
--
Lorenzo Hernández García-Hierro [1024D/6F2B2DEC]
Hardened Debian head developer & project manager.
http://www.debian-hardened.org
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-12-04 20:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1102192723.19001.19.camel@localhost \
--to=lorenzo@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox