From: philipp.ammann@posteo.de
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Unofficial hardened-sources ebuilds?
Date: Tue, 15 Aug 2017 22:39:30 +0200 [thread overview]
Message-ID: <6b567d69b43dc136d3dea0aeca5a4886@posteo.de> (raw)
In-Reply-To: <20170815191318.GH2141@home.power>
Am 15.08.2017 21:13 schrieb Alex Efros:
> [...]
>>
>> [3] https://github.com/minipli/linux-unofficial_grsec
>> [4] https://github.com/copperhead/linux-hardened
>
> Sounds cool, but is anyone is going to provide ebuilds for these
> kernels?
> Not official, but having these in some overlay is better than nothing.
You don't really need an ebuild. What I do is manually install
sys-devel/bc and then:
cd /usr/src
git clone --single-branch --branch=linux-4.9.x-unofficial_grsec
git://github.com/minipli/linux-unofficial_grsec.git grsec
ln -s grsec linux
(You 'need' the linux symlink for ebuilds to be able to check .config
options)
Whenever there is a new release simply run 'git pull'.
Cheers
Philipp
next prev parent reply other threads:[~2017-08-15 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 19:13 [gentoo-hardened] Unofficial hardened-sources ebuilds? Alex Efros
2017-08-15 20:39 ` philipp.ammann [this message]
2017-08-15 21:33 ` Alex Efros
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=6b567d69b43dc136d3dea0aeca5a4886@posteo.de \
--to=philipp.ammann@posteo.de \
--cc=gentoo-hardened@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox