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.

Sign up for GitHub

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

Jump to bottom

MIT krb5 refuses to inquire about partially established contexts #69

Closed
DirectXMan12 opened this issue Jun 5, 2015 · 0 comments
Closed

MIT krb5 refuses to inquire about partially established contexts #69

DirectXMan12 opened this issue Jun 5, 2015 · 0 comments
Assignees
@DirectXMan12
Labels
bug
Milestone
1.1.2

Comments

@DirectXMan12
Copy link
Member

MIT krb5 refuses to inquire about partially established contexts, meaning SecurityContext.complete will fail unless it would return True. This hasn't been an issue so far, since MIT krb5 negotiation seems to generally complete in one round trip. However, it could be an issue in the future.
@DirectXMan12 DirectXMan12 self-assigned this Jun 5, 2015
@DirectXMan12 DirectXMan12 added this to the 1.1.2 milestone Jun 5, 2015
DirectXMan12 added a commit that referenced this issue Jun 5, 2015
@DirectXMan12
Don't inquire about incomplete security contexts
2fe3c19 
This commit changes `SecurityContext` to handle a couple of cases where
we called `_inquire` when the context was not fully established.  A bug
in MIT krb5 prevents this from working properly.

In the case of `complete`, we simply cache the result of the last
`step` call.

Fixes #69
@DirectXMan12 DirectXMan12 mentioned this issue Jun 5, 2015
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DirectXMan12 DirectXMan12

Labels
bug
Projects
None yet
Milestone
1.1.2
Development

No branches or pull requests
1 participant
@DirectXMan12