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

GSS_C_MA_AUTH_INIT_ANON #9

Open
lhoward opened this issue Apr 6, 2020 · 5 comments · May be fixed by #27
Open

GSS_C_MA_AUTH_INIT_ANON #9

lhoward opened this issue Apr 6, 2020 · 5 comments · May be fixed by #27

Comments

@lhoward
Copy link

lhoward commented Apr 6, 2020

If you support GSS_C_ANON_FLAG, you should list GSS_C_MA_AUTH_INIT_ANON as a supported mechanism attribute. Future versions of Heimdal may exclude mechanisms from negotiation that do not support this attribute, if the initiator requested GSS_C_ANON_FLAG.

@simo5
Copy link
Collaborator

simo5 commented Apr 6, 2020

TBH I am not sure I ever tested anonymous support, so I am going to assume it is somewhat broken.
I will try to validate and then add GSS_C_MA_AUTH_INIT_ANON as part of resolving this issue.

@lhoward
Copy link
Author

lhoward commented Apr 6, 2020

Thanks Simo. Not sure if this mechanism was ever used with Heimdal, anyway? But it's nice for things to be "correct".

@simo5
Copy link
Collaborator

simo5 commented May 18, 2020

I currently do not allow anon:

if (claimant_cred_handle == GSS_C_NO_CREDENTIAL) {
    if (req_flags & GSS_C_ANON_FLAG) {
        set_GSSERRS(ERR_NOARG, GSS_S_UNAVAILABLE);
        goto done;

@lhoward
Copy link
Author

lhoward commented May 19, 2020

Ah, then no issue then. But – if you do want to support it, then please advertise GSS_C_MA_AUTH_INIT_ANON too. :)

@lhoward lhoward closed this as completed May 19, 2020
@simo5
Copy link
Collaborator

simo5 commented May 19, 2020

I am working on it, please do not close this issue :)

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