All of lore.kernel.org
 help / color / mirror / Atom feed
From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH/RFC] Haveged definition
Date: Wed, 20 Jul 2011 17:17:32 +0200	[thread overview]
Message-ID: <20110720151732.GA18841@siphos.be> (raw)

Haveged is a simple daemon that feeds the systems' random pool entropy using
the HAVEGE algorithm. 

The following posts contain the .te, .if, .fc as well as the sysadm role
enhancement to be able to manage the haveged process.

My suggestion is to stick this in the services/ category. Yet, if there is a
consensus that we don't want all services (especially relatively simple
ones) in the reference policy, then that is fine by me as well.

Wkr,
	Sven Vermeulen

             reply	other threads:[~2011-07-20 15:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20 15:17 Sven Vermeulen [this message]
2011-07-20 15:19 ` [refpolicy] [PATCH 1/4] Adding haveged TE definition Sven Vermeulen
2011-07-20 15:19 ` [refpolicy] [PATCH 2/4] Adding haveged IF definition Sven Vermeulen
2011-07-20 15:20 ` [refpolicy] [PATCH 3/4] Adding haveged FC definition Sven Vermeulen
2011-07-20 15:33 ` [refpolicy] [PATCH/RFC] Haveged definition Christopher J. PeBenito
2011-07-20 15:35   ` Sven Vermeulen

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=20110720151732.GA18841@siphos.be \
    --to=sven.vermeulen@siphos.be \
    --cc=refpolicy@oss.tresys.com \
    /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.