{'fraction_non_alphanumeric': 0.01734820322180917, 'fraction_numerical': 0.0, 'mean_word_length': 5.464, '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}}
System configuration as a privilege

We present a new approach for separating configuration privilege from traditional root privilege. We limit this new configuration privilege to a single (new) system daemon, configd. This daemon reads requests for changes in system configuration, either allowing or denying each request based on various criteria (possibly including user input). We do not allow any other application to run with configuration permission, forcing all requests for a change in system configuration to be processed by configd. We discuss the basic functionality required for configd to protect system configuration, and some preliminary improvements to a basic prototype design. We concentrate on only those system configuration changes performed through the modification of a file on disk.