From: Matthias-Christian Ott <ott@mirix.org>
To: linux-crypto@vger.kernel.org
Subject: Why does CRYPTO_USER require CAP_NET_ADMIN?
Date: Sat, 05 Apr 2014 16:43:44 +0200 [thread overview]
Message-ID: <534016A0.6020702@mirix.org> (raw)
If I'm not mistaken, CRYPTO_USER requires CAP_NET_ADMIN for all
requests. Is there any reason for this requirement for read-only requests?
I think read-only requests should not require CAP_NET_ADMIN. An example
where this is important is important is AF_ALG. I'm working on AF_ALG
support for GnuTLS, encryption and decryption via AF_ALG does not
require special capabilities. However, retrieving the cipher priority to
determine whether the cipher is hardware accelerated does require
CAP_NET_ADMIN.
Regards,
Matthias-Christian
next reply other threads:[~2014-04-05 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 14:43 Matthias-Christian Ott [this message]
2014-04-24 22:51 ` [PATCH] crypto: user - Allow CRYPTO_MSG_GETALG without CAP_NET_ADMIN Matthias-Christian Ott
2014-04-28 21:37 ` Marek Vasut
2014-04-30 19:23 ` Matthias-Christian Ott
2014-05-01 10:53 ` Marek Vasut
2014-05-03 23:45 ` Matthias-Christian Ott
2014-05-08 14:01 ` Herbert Xu
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=534016A0.6020702@mirix.org \
--to=ott@mirix.org \
--cc=linux-crypto@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).