lustre-devel-lustre.org archive mirror
 help / color / mirror / Atom feed
From: "Degremont, Aurelien" <degremoa@amazon.com>
To: Amir Shehata <amir.shehata.whamcloud@gmail.com>,
	Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [lustre-devel] o2iblnd/socklnd security
Date: Wed, 6 Jan 2021 09:33:42 +0000	[thread overview]
Message-ID: <7826A5FF-2C3C-4B6A-88A5-A4C6123F390C@amazon.com> (raw)
In-Reply-To: <CAAqp6i0+WcOhW8cOYZSrZu+UMAgaDMA=zZnfbtJW--Nk9PQ44A@mail.gmail.com>


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

Based on my experience, people usually enforced privileged ports (this is default anyway, no?)
I only see complex setups where this could be a problem for admin, but what problem this option is causing to you?

You should probably send that to lustre-discuss if you want to have a simple survey of what people are using.

De : lustre-devel <lustre-devel-bounces@lists.lustre.org> au nom de Amir Shehata <amir.shehata.whamcloud@gmail.com>
Date : mercredi 6 janvier 2021 à 00:18
À : Lustre Development List <lustre-devel@lists.lustre.org>
Objet : [EXTERNAL] [lustre-devel] o2iblnd/socklnd security


CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.


Hi,

Currently o2iblnd has two parameters

use_privileged_port and require_privileged_port to control the port range to use. They control whether to use/accept a privileged port (1 -1023) or any port.

Similarly socklnd has a similar parameter: accept_type. If set to "all" then any port range is accepted otherwise, only a privileged port is accepted.

I'm trying to get a better idea of how these are being used on sites. And if so do sites value this level of control? IE do these parameters provide a level of security which is deemed valuable?

thanks
amir

[-- Attachment #1.2: Type: text/html, Size: 5027 bytes --]

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

_______________________________________________
lustre-devel mailing list
lustre-devel@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org

           reply	other threads:[~2021-01-06  9:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAAqp6i0+WcOhW8cOYZSrZu+UMAgaDMA=zZnfbtJW--Nk9PQ44A@mail.gmail.com>]

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=7826A5FF-2C3C-4B6A-88A5-A4C6123F390C@amazon.com \
    --to=degremoa@amazon.com \
    --cc=amir.shehata.whamcloud@gmail.com \
    --cc=lustre-devel@lists.lustre.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).