Re: Current semantics for channel-bindings in GSSAPI
Stefan Metzmacher <[email protected]>
| Newsgroups | gmane.comp.encryption.kerberos.devel |
|---|---|
| Message-ID | <[email protected]> |
Am 10.03.20 um 16:34 schrieb Isaac Boukris: > On Tue, Mar 10, 2020 at 4:23 PM Stefan Metzmacher <[email protected]> wrote: >> >> Hi Issac, >> >>> As discussed last week, we want the following changes. >>> >>> - MIT should match Heimdal behavior and only error if client bindings >>> are not all zeros. >>> - Both Heimdal/MIT should return channel-bound flag if the bindings did match. >>> - Both Heimdal/MIT should take advantage of KERB_AP_OPTIONS_CBT if >>> present if authenticator, in which case if the server passed bindings >>> they must match. >>> - Both Heimdal/MIT should provide a conf option to asset the client >>> system supports channel-bindings, causing KERB_AP_OPTIONS_CBT to be >>> sent in any ap-req. >>> >>> I submitted wip PR #1047 upstream MIT based on the above. >>> >>> @metze, would that satisfy samba's requirements? >> >> I looked briefly and the core changes look good, >> but (as always :-) I think krb5.conf option alone are unflexible >> and I'd really like to get rid of autogenerated krb5.conf files and >> global exporting "KRB5_CONFIG". So APIs to turn this on from the >> application would be great. > > Ok, so we'd need a new cred-option to override it by the application. If we can agree on a way to implement that:-) Using gss_set_cred_option() would be the simplest solution, but it got rejected for GSS_KRB5_CRED_NO_TRANSIT_CHECK_X. Passing cred_store to gss_acquire_cred_from() would also work and I'm not sure if/how gss_create_sec_context() + gss_set_sec_context_option() would work. gss_set_sec_context_option() would be the most flexible way and may be useful for more things I plan to implement. metze _______________________________________________ krbdev mailing list [email protected] https://mailman.mit.edu/mailman/listinfo/krbdev
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEfFbGo3YXpfgryIw9DbX1YShpvVYFAl5nuB8ACgkQDbX1YShp vVZbNQ/+Ox9dBdqXWrwfUyfzxwc9SZSILN8nqqEKVpCswnTIboiWvLERBQU98oOH BkTj6U7PI8dBsdyTTlbTqJ4hxqTVLTMvrh/L6mYxj9ssAalN1DwuP4+Bt+GV4tCd JbC1akgmDJ/xIIfQUaj2bN4mFPhqiEh9EKgzXTitslv3Pw1Zvq23WLrae6cfdRMc 4XHeUQP1B4Wi310ELjGQ71eoWTyQ+VlaE5op8GN+6dlgzkQnvQ3aPpaj3cog7Qdg jxLdasOA75Yryds0aikMMagSqPqAzucWuiT+9Md6J/p8schz/MqDP1ARmHdfCpRc pQW5mgyC0t4ZAnWGgFeX1bNfema01WbA21dl/Rl5j12LFEhNNDfRGJ1qcVvecAH7 p4rhMt2zGjR2tTJenwgRzCCWb1pwwxHcdSyhSkmqIkOXsE1SQ/UYc+2phhWcOYCA TTqgbbTIh+lDlafE/c3VGQiU1i9bE6VLgh6j9JhLST2+ojZwgAG9Dyb+kydc/Af4 9WADu0gAPOBxCSK7LsdbPn74vOJdXnVSLiLum/qf7CcP6D6qs4Z4q7QNnCsYz5g6 dImppVrHXXWMkRFTW7iLqdPGxarRgw3/+DlVG1m6hOPB5PeJLAAWcDU3NW29L3hS Iv1uIScvXAOV94+b7ZintPkOBq8sVyhhWNIZx1zsd3BzdvCJowQ= =fqwI -----END PGP SIGNATURE-----