The following Haskell programs, built by GHC, need unconfined_execmem_exec_t
added to the SELinux policies:
Tibbs suggests that Haddock doesn't need to be blocked on this.
Why doesn't haddock fix their code to not need execmem?
Is this java or mono?
What does haddock need both executable and writeable memory at the same time?
(In reply to comment #2)
> Is this java or mono?
The runtime system for programs compiled by GHC generates code dynamically and
The interaction with SELinux's enforcing mode is a known problem, which was
previously addressed with a hack: the %post scripts for Haskell programs were
using chcon to add unconfined_exec_mem_t. This obviously didn't work in lots of
circumstances, hence wanting to apply the policy properly.
The underlying problem, namely the way GHC allocates memory that it intends to
execute dynamically, should be fixed within the next six months or so. See
http://hackage.haskell.org/trac/ghc/ticket/738 for details.
Fixed in selinux-policy-3.3.1-74.fc9.noarch
Can Haskell users verify this and close the bug if it's fixed?
I started a comment long ago (which was then lost by a browser crash or restart)...
Basic summary is most (all) haskell programs shipped can run now in enforcing.
However there have been a number of path changes that should probably be updated
in selinux-policy. I can help to do that.
Currently the changes needed are being done for that at install time.
What are the paths?
I tested in F11 and it seems AFAICT the %post stuff we have is no longer needed for ghc executables so I am removing it for f12.