On Tue, 2022-07-19 at 22:17 +0000, Kenneth Goldman wrote:
> On Mon, 2022-07-18 at 17:36 +0000, Kenneth Goldman wrote:
> > It depends.
> > Windows seems to have a large keystore, so you probably don't
> > have to
> > ever flush.
> > Linux in kernel RM manages keys across processes but not within
> > processes, so you still have to flush.
> This is also how TBS works on Windows.
Not on my Windows 10. I just created 32 keys with one process. Now
32 loaded keys.
Did the process exit? I always thought TBS was spec compliant:
"The RM also monitors connections, and removes table entries and
ContextFlushes leftover sessions
when the caller closes a connection." from Section 2.3.3 of:
The table entries include transient handles and their associated
OK, the Windows RM swaps them out, but the application never
I don't know what the RM limit is, but it's certainly far more than
getcapability.exe -cap 1 -pr 80000000
These look like virtual handles. The spec also states,
"In responses that return handles, these handles MUST be virtualized
before returning the
response to the caller:
These virtual handles MUST be unique per connection".
I don't think anyone actually makes them unique per connection.