openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@ozlabs.org>
To: Joseph Reynolds <jrey@linux.ibm.com>, openbmc <openbmc@lists.ozlabs.org>
Subject: Re: Security Working Group meeting - Wednesday September 18 - results
Date: Thu, 19 Aug 2021 08:49:11 +0800	[thread overview]
Message-ID: <e6ff536d22764e44ac9444c50bad41d4b4a1d8c1.camel@ozlabs.org> (raw)
In-Reply-To: <911133cc-791b-5cec-4de9-c2d9f85f7e82@linux.ibm.com>

Hi Joseph,

> 5 How to add session timeouts to host console?
> 
> DISCUSSION:
> 
> See the diagram in the README under 
> https://github.com/openbmc/obmc-console 
> <https://github.com/openbmc/obmc-console>.
> 
> We thought obmc-console-client was the right place to implement the 
> timeout mechanism.

OK, but that diagram doesn't really cover the detail you'd need to base
such a decision on; there's the ssh server between port 2222 and the
obmc-console-client program.

[obmc-console-client is just a *really* simple bridge between stdio and
a unix domain socket. It doesn't own the network socket, nor do any
authentication or authorisation]

We can definitely do an optional timeout in obmc-console-client, but I
want to make sure that's really what you want first.

Cheers,



Jeremy


  reply	other threads:[~2021-08-19  0:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 13:54 Security Working Group meeting - Wednesday September 18 Joseph Reynolds
2021-08-18 17:33 ` Patrick Williams
2021-08-18 19:12   ` Joseph Reynolds
2021-08-18 19:32 ` Security Working Group meeting - Wednesday September 18 - results Joseph Reynolds
2021-08-19  0:49   ` Jeremy Kerr [this message]
2021-08-20 16:19     ` Security Working Group meeting - Wednesday September 18 - results - add idle timeout Joseph Reynolds

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=e6ff536d22764e44ac9444c50bad41d4b4a1d8c1.camel@ozlabs.org \
    --to=jk@ozlabs.org \
    --cc=jrey@linux.ibm.com \
    --cc=openbmc@lists.ozlabs.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).