From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Sriram Yagnaraman <sriram.yagnaraman@ericsson.com>,
Jakub Grajciar <jgrajcia@cisco.com>
Subject: Re: [PATCH 7/7] doc: clarify memif secret is not access control
Date: Mon, 28 Sep 2026 10:56:53 -0700 [thread overview]
Message-ID: <20260928105653.1b8443e9@phoenix.local> (raw)
In-Reply-To: <20260922194138.508919-8-stephen@networkplumber.org>
On Tue, 22 Sep 2026 12:40:58 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:
> The secret option was described as a security option, which invites
> using it as one. It is sent in cleartext in the connection request,
> and when passed as a device argument it is visible to other local
> users in the process arguments.
>
> Describe it as what it is, a check against connecting mismatched
> interfaces, and document what actually restricts access to an
> interface. By default the control socket is in the abstract
> namespace and has no filesystem entry to own or permission. Only
> with socket-abstract=no do file permissions and the owner-uid and
> owner-gid options apply.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Tested-by: Sriram Yagnaraman <sriram.yagnaraman@ericsson.com>
> ---
Recheck-request: aws-unit-testing
next prev parent reply other threads:[~2026-09-28 17:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 19:40 [PATCH 0/7] net/memif: validate input from connecting peer Stephen Hemminger
2026-09-22 19:40 ` [PATCH 1/7] maintainers: update for memif driver Stephen Hemminger
2026-09-22 19:40 ` [PATCH 2/7] net/memif: fix issues in statistics Stephen Hemminger
2026-09-22 19:40 ` [PATCH 3/7] net/memif: validate peer descriptors Stephen Hemminger
2026-09-22 19:40 ` [PATCH 4/7] net/memif: validate control channel requests Stephen Hemminger
2026-09-22 19:40 ` [PATCH 5/7] net/memif: validate descriptor length in zero-copy mode Stephen Hemminger
2026-09-22 19:40 ` [PATCH 6/7] net/memif: add server/client connectivity test Stephen Hemminger
2026-09-22 19:40 ` [PATCH 7/7] doc: clarify memif secret is not access control Stephen Hemminger
2026-09-24 15:44 ` Stephen Hemminger
2026-09-28 17:56 ` Stephen Hemminger [this message]
2026-09-24 11:24 ` [PATCH 0/7] net/memif: validate input from connecting peer Sriram Yagnaraman
2026-09-29 15:42 ` Stephen Hemminger
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=20260928105653.1b8443e9@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=sriram.yagnaraman@ericsson.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox