On Mon, May 12, 2014 at 5:19 PM, Gilles Chehade gil...@poolp.org wrote:
We have abused the term privsep, in this particular case it's not
really privileges separation but really vmem. space separation. The
goal was to isolate that code from the network, it could be done in
the lookup process
On Tue, May 13, 2014 at 07:08:10PM +0200, Jason A. Donenfeld wrote:
On Mon, May 12, 2014 at 5:19 PM, Gilles Chehade gil...@poolp.org wrote:
We have abused the term privsep, in this particular case it's not
really privileges separation but really vmem. space separation. The
goal was to
On Fri, May 09, 2014 at 06:49:50PM +0200, Jason A. Donenfeld wrote:
On Thu, May 8, 2014 at 2:56 PM, Gilles Chehade gil...@poolp.org wrote:
On Thu, May 08, 2014 at 05:08:36AM +0200, Jason A. Donenfeld wrote:
no, no new UID/username required
Curious, then, as to what kind of privsep
On Thu, May 8, 2014 at 2:56 PM, Gilles Chehade gil...@poolp.org wrote:
On Thu, May 08, 2014 at 05:08:36AM +0200, Jason A. Donenfeld wrote:
no, no new UID/username required
Curious, then, as to what kind of privsep this provides...
On Thu, May 08, 2014 at 05:08:36AM +0200, Jason A. Donenfeld wrote:
On Wed, May 7, 2014 at 4:43 PM, gil...@poolp.org wrote:
- RSA engine privsep by reyk@
- ca process, by reyk
Do these require new UIDs/usernames?
no, no new UID/username required
--
Gilles Chehade
On Wed, May 7, 2014 at 4:43 PM, gil...@poolp.org wrote:
- RSA engine privsep by reyk@
- ca process, by reyk
Do these require new UIDs/usernames?
