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

client referral: return correct client principal in case of a wrong realm #323

Closed
wants to merge 1 commit into from

Conversation

abbra
Copy link

@abbra abbra commented Sep 3, 2015

prepare_error_as_req() gets protocol error code but compares it with
table code and misses to add proper client principal as returned by the
DAL driver.

Rework the code to avoid errcode comparison within prepare_error_as_req().

…ealm

prepare_error_as_req() gets protocol error code but compares it with
table code and misses to add proper client principal as returned by the
DAL driver.

Rework the code to avoid errcode comparison within
prepare_error_as_req().
@greghudson
Copy link
Member

Please review the top two commits at https://github.com/greghudson/krb5/commits/client_referral as a counterproposal.

I'm no longer sure that I like the idea of changing the code to pass an unconditional client princ to prepare_error_as(); it adds too much complexity to finish_as_req() which is in dire need of refactoring (a perennial problem for the KDC code). It might be better to push more responsibility down into prepare_error_as(), perhaps passing it the state pointer instead of a half-dozen fields of it. I will defer that work to a later time.

@abbra
Copy link
Author

abbra commented Sep 3, 2015

I'm fine with your patch If you want to do refactoring of prepare_error_as() later.

@tlyu
Copy link
Member

tlyu commented Sep 14, 2015

@greghudson your patches look OK to me.

@greghudson
Copy link
Member

Pushed to master as 4e036ef 1e4a039

@greghudson greghudson closed this Sep 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants