public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: Antoine Martin <antoine@nagafix.co.uk>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] mysql 4.1 requires shlib_t:file execmod?
Date: Tue, 25 Oct 2005 11:45:37 +0100	[thread overview]
Message-ID: <1130237137.10477.5.camel@localhost.localdomain> (raw)
In-Reply-To: <435D84D9.26102.B0B60317@pageexec.freemail.hu>

On Tue, 2005-10-25 at 01:05 +0200, pageexec@freemail.hu wrote:
> On 24 Oct 2005 at 22:29, Antoine Martin wrote:
> > USE="-X mysql sasl ipv6 nptl hardened"
> > 
> > dev-db/mysql-4.1.14  +berkdb -big-tables -cluster -debug -doc -extraengine
> > -geometry -minimal +perl +readline +selinux +ssl -static +tcpd -utf8
> 
> ok, mine's exactly the same except for +selinux (no selinux here).
> so it's either that or the hardened toolchain that causes this,
> although i don't see from the ebuild nor from the toolchain how
> that extra crypto enters the picture. anyone has ideas? also, can
> you try to emerge it without selinux and/or the hardened toolchain
> (set gcc-config to the normal specs file) and see what happens?
Sure. But how do I do that?
(good thing that box is not a proper live one!)

>  if
> that cures it, comparing compile/emerge logs might shed a light on
> this.
Also, do you know how I can contribute some selinux policy files to gentoo?

Thanks
Antoine

-- 
gentoo-hardened@gentoo.org mailing list



  reply	other threads:[~2005-10-25 10:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-22 14:15 [gentoo-hardened] mysql 4.1 requires shlib_t:file execmod? Antoine Martin
2005-10-22 14:39 ` Dave Strydom
2005-10-22 16:33   ` Antoine Martin
2005-10-22 16:38     ` Antoine Martin
2005-10-22 14:53 ` pageexec
2005-10-22 15:45   ` Antoine Martin
2005-10-22 15:53     ` pageexec
2005-10-22 16:37       ` Antoine Martin
2005-10-22 17:24         ` pageexec
2005-10-22 17:31           ` Antoine Martin
2005-10-22 17:56             ` Petre Rodan
2005-10-23 20:42               ` Antoine Martin
2005-10-24 13:47                 ` pageexec
2005-10-24 19:15                   ` Antoine Martin
2005-10-24 21:23                     ` pageexec
2005-10-24 21:29                       ` Antoine Martin
2005-10-24 23:05                         ` pageexec
2005-10-25 10:45                           ` Antoine Martin [this message]
2005-10-25 12:04                             ` pageexec
2005-10-25 18:52                           ` solar
2005-10-25 20:55                             ` [gentoo-hardened] " Antoine Martin
2005-10-22 17:31         ` [gentoo-hardened] " solar
2005-10-22 17:41           ` Antoine Martin
2005-10-22 18:10             ` solar
2005-10-23 17:54               ` [gentoo-hardened] SELinux n00b questions Dale Pontius
2005-10-26 22:59                 ` Chris PeBenito
2005-10-27  1:33                   ` Dale Pontius
2005-10-31  3:19                     ` Chris PeBenito
2005-11-14  1:51                       ` Dale Pontius
2005-11-14  8:20                         ` Peter Shaw
2005-11-14 22:37                           ` Dale Pontius
2005-11-14 22:53                             ` Antoine Martin
2005-11-15  1:23                             ` Dale Pontius
2005-10-23 19:06               ` [gentoo-hardened] mysql 4.1 requires shlib_t:file execmod? Antoine Martin

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=1130237137.10477.5.camel@localhost.localdomain \
    --to=antoine@nagafix.co.uk \
    --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