On Thu, 28 Feb 2013, Benjamin Kaduk wrote:
On Thu, 28 Feb 2013, Simon Wilkinson wrote:
On 28 Feb 2013, at 22:05, Benjamin Kaduk wrote:
All I see looking nowis discussion of using the maxcalls information as a
way to migrate to having more than 4 calls per connection, which doesn't
sound familiar. We also don't mention whether call numbers in use are
checked as part of verifying the authenticator -- I do not currently do
so.
You should just provide the call number vector to the RX layer, which will
take care of checking the call numbers within it (OpenAFS's RX currently
just sets up the connection according to the provided authenticator, which
will cause non-matching calls to fail as they are encountered)
Oh, hmm, I guess rxi_SetCallNumberVector is exported.
We should probably adjust the description of
RXGK_Authenticator.call_numbers, as my first reading of it was that the
variable-length array was only to include active calls, not the whole
vector. Perhaps something about "all available call channels" on this
connection?
-Ben
_______________________________________________
AFS3-standardization mailing list
[email protected]
http://lists.openafs.org/mailman/listinfo/afs3-standardization
