From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ken Goldman <kgoldman@us.ibm.com>, tpmdd-devel@lists.sourceforge.net
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion
Date: Fri, 27 Jan 2017 13:59:15 -0800 [thread overview]
Message-ID: <1485554355.3229.15.camel@HansenPartnership.com> (raw)
In-Reply-To: <o6gdhu$li$1@blaine.gmane.org>
On Fri, 2017-01-27 at 16:20 -0500, Ken Goldman wrote:
> On 1/19/2017 7:41 AM, Jarkko Sakkinen wrote:
> >
> > I actually think that the very best solution would be such that
> > sessions would be *always* lease based. So when you create a
> > session you would always loose within a time limit.
> >
> > There would not be any special victim selection mechanism. You
> > would just loose your session within a time limit.
>
> I worry about the time limit.
>
> I have a proposed use case (policy signed) where the user sends the
> session nonce along with a "payment" to a vendor and receives back a
> signature authorization over the nonce.
>
> The time could be minutes or even hours.
So the problem is that sessions are a limited resource and we need a
way to allocate them when under resource pressure. Leasing is the
fairest way I can think of but I'm open to other mechanisms if you
propose them.
Note that the lease mechanism doesn't mean every session expires after
the limit, it just means that every session becomes eligible for
reclaim after the limit. If there's no-one else waiting, you can keep
your session for hours.
James
next prev parent reply other threads:[~2017-01-27 22:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 20:48 [RFC] tpm2-space: add handling for global session exhaustion James Bottomley
2017-01-19 12:25 ` [tpmdd-devel] " Jarkko Sakkinen
2017-01-19 12:41 ` Jarkko Sakkinen
[not found] ` <o6gdhu$li$1@blaine.gmane.org>
2017-01-27 21:59 ` James Bottomley [this message]
2017-01-19 12:59 ` James Bottomley
2017-01-20 13:40 ` Jarkko Sakkinen
[not found] ` <o6gese$pev$1@blaine.gmane.org>
2017-01-27 22:04 ` James Bottomley
2017-01-27 23:35 ` Jason Gunthorpe
2017-01-27 23:48 ` James Bottomley
2017-01-30 0:52 ` Ken Goldman
2017-01-30 16:04 ` [tpmdd-devel] " James Bottomley
2017-01-30 21:58 ` Jarkko Sakkinen
2017-01-30 22:13 ` James Bottomley
2017-01-31 13:31 ` Jarkko Sakkinen
[not found] ` <o6qog0$30l$1@blaine.gmane.org>
2017-01-31 19:55 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2017-02-09 9:06 Dr. Greg Wettstein
2017-02-09 15:19 ` Jarkko Sakkinen
2017-02-09 19:04 ` Jason Gunthorpe
2017-02-09 19:29 ` James Bottomley
2017-02-09 21:54 ` Jason Gunthorpe
2017-02-10 8:48 ` Jarkko Sakkinen
2017-02-09 19:24 ` James Bottomley
2017-02-09 20:05 ` James Bottomley
2017-02-10 10:03 Dr. Greg Wettstein
2017-02-10 16:46 ` James Bottomley
2017-02-12 20:29 ` Ken Goldman
[not found] ` <OFA049276F.2B32440E-ON852580C3.00742287-852580C3.00748E6B@notes.na.collabserv.com>
2017-02-14 14:38 ` Dr. Greg Wettstein
2017-02-14 16:47 ` James Bottomley
[not found] ` <71dc0e80-6678-a124-9184-1f93c8532d09@linux.vnet.ibm.com>
2017-02-16 20:06 ` Dr. Greg Wettstein
2017-02-16 20:33 ` Jarkko Sakkinen
2017-02-17 9:56 ` Dr. Greg Wettstein
2017-02-17 12:37 ` Jarkko Sakkinen
2017-02-17 22:37 ` Dr. Greg Wettstein
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=1485554355.3229.15.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=kgoldman@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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