From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] libgcrypt: update 1.7.3 -> 1.7.5
Date: Tue, 10 Jan 2017 16:38:38 +0100 [thread overview]
Message-ID: <20170110153837.GA13029@archie.localdomain> (raw)
In-Reply-To: <20170110150921.sjlgnhych3v4g5u7@pengutronix.de>
Hi Michael,
On Tue, Jan 10, 2017 at 04:09:21PM +0100, Michael Olbrich wrote:
> Hmm, I looked at what the capabilities stuff is for. It is used for 'secure
> memory'. I'm not an expert here, but I guess it will set up some memory
> that cannot be swapped out etc. It only needs libcap and that's a rather
> small library, so I think this should be enabled. What do you think?
Yeah, why not. libcap does not hurt.
I first thought it would use secmem even without capabilities but before
the setuid privileges are dropped, secmem is disabled. So it seems
necessary.
We should probably also update libcap to 2.25. There they dropped the
dependency to libattr.
>
> Looks good otherwise. No need to send a new patch. I'll make the change if
> necessary.
Great, thanks.
Clemens
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2017-01-10 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 18:07 Clemens Gruber
2017-01-10 15:09 ` Michael Olbrich
2017-01-10 15:38 ` Clemens Gruber [this message]
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=20170110153837.GA13029@archie.localdomain \
--to=clemens.gruber@pqgruber.com \
--cc=ptxdist@pengutronix.de \
/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