All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@tnetconsulting.net>
To: kernelnewbies@kernelnewbies.org
Subject: Re: Opening /proc/<pid>/net/dev prevents network namespace from expiring
Date: Mon, 24 Aug 2020 10:53:51 -0600	[thread overview]
Message-ID: <6ee04d29-e903-75bf-1188-85ad196f23cf@tnetconsulting.net> (raw)
In-Reply-To: <CAEyJRx0Zd_jtH1JQCSYYrdc-YTa8yvtneaurUKXEKK32-kWfRA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 675 bytes --]

On 8/22/20 3:05 PM, Arne Welzel wrote:
> Hello,

Hi,

> as an unprivileged user one is able to keep network namespaces from 
> expiring by opening /proc/<pid>/net/dev of other processes.

This is what I would expect.

At least based on my understanding of how the various namespaces work. 
If something is using the namespace, it's not removed.  Opening a file / 
device therein would count as using it.

> Does that seem like problematic behavior?

No, not as such.

This seems to me like a permissions issue on the /proc/<pid> directory.

Read:  Set the permissions such that access is restricted appropriately.



-- 
Grant. . . .
unix || die


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4013 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  parent reply	other threads:[~2020-08-24 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-22 21:05 Opening /proc/<pid>/net/dev prevents network namespace from expiring Arne Welzel
2020-08-24  7:42 ` Greg KH
2020-08-24 16:53 ` Grant Taylor [this message]
2020-08-24 21:49 Arne Welzel

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=6ee04d29-e903-75bf-1188-85ad196f23cf@tnetconsulting.net \
    --to=gtaylor@tnetconsulting.net \
    --cc=kernelnewbies@kernelnewbies.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 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.