You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know whether the implementation of the krb5.conf file is meant to be fully compatible with MIT Kerberos (which defined the file) but posting anyway.
which, if I understand the code correctly, treats example.com as an exact match and .example.com as a suffix match.
According to krb5/krb5@8f5ce82, however, that's not how MIT Kerberos handles it – their docs claimed it did but that
didn't match the code, and they chose to keep the code behavior and change docs. So instead, a plain example.com matches itself and subdomains (unless overridden by an explicit .example.com setting), whereas .example.com only matches subdomains but not itself.
(I don't know how Heimdal Kerberos handles it; couldn't figure out the code.)
The text was updated successfully, but these errors were encountered:
I don't know whether the implementation of the krb5.conf file is meant to be fully compatible with MIT Kerberos (which defined the file) but posting anyway.
#326 added:
which, if I understand the code correctly, treats
example.com
as an exact match and.example.com
as a suffix match.According to krb5/krb5@8f5ce82, however, that's not how MIT Kerberos handles it – their docs claimed it did but that
didn't match the code, and they chose to keep the code behavior and change docs. So instead, a plain
example.com
matches itself and subdomains (unless overridden by an explicit.example.com
setting), whereas.example.com
only matches subdomains but not itself.(I don't know how Heimdal Kerberos handles it; couldn't figure out the code.)
The text was updated successfully, but these errors were encountered: