Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Token size specification #94

Closed
lambdax-x opened this issue Feb 15, 2016 · 4 comments
Closed

Token size specification #94

lambdax-x opened this issue Feb 15, 2016 · 4 comments

Comments

@lambdax-x
Copy link

When performing a negociation step such as shown in the code proposed in the documentation, it is not specified what size the client and the service should expect for an incoming token.

@DirectXMan12
Copy link
Member

Can you clarify what your issue is here?. Applications making use of GSSAPI are expected to define a protocol for transmitting the token that includes details like how much the other end of the connection needs to read to obtain the whole token.

@lambdax-x
Copy link
Author

I could send the token along with its size computed on the fly of course but I was wondering if the token size is fixed or, at least, bounded.

@simo5
Copy link
Contributor

simo5 commented Feb 15, 2016

It is mechanism specific and there is no fixed size.

@lambdax-x
Copy link
Author

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants