{'fraction_non_alphanumeric': 0.016408386508659983, 'fraction_numerical': 0.0009115770282588879, 'mean_word_length': 5.066298342541437, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Cross-realm Kerberos implementations

When someone wants to use a service, a person has to provide credentials. These credentials have to be remembered by the user and also needs to be filled in everywhere. This is where Kerberos comes in. With the help of Kerberos its single sign-on possibilities and cross-realm capabilities, this could all be taken care of for the user. This would require several Kerberos KDCs configured with trust relationships. Due to the nature of Kerberos and its philosphy of shared keys this imposes a heavy administrative burden. We look at four major implementations, namely Heimdal, MIT Kerberos 5, GNU Shishi and Active Directory. This paper describes the research that has been conducted to see how well these four implementations of Kerberos work together and highlight several points of interest when using these implementations in a mixed environment. Furthermore we discuss several focus points that play an important role in cross-realm behaviour and techniques that may assist in accomplishing dynamic configuration and easing the administrative complexity.