{'fraction_non_alphanumeric': 0.030303030303030304, 'fraction_numerical': 0.004887585532746823, 'mean_word_length': 5.059171597633136, '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}}
ConCert: Content Revocation Using Certificates

Content reuse on the Web is becoming even more common since the Web 2.0 “phenomenon”. However, each time content is reused certain information is either completely lost (for example through excerpts) or gets harder to verify. This reduces the content’s quality and thus the content’s value for viewers. Among the lost information are origin, author, creation time, or if the author still endorses the content. We propose preserving this information in a cryptographically protected content certificate (ConCert). This X.509 compatible certificate binds the content to the author’s public-key. Using a hash tree we allow viewers to verify the properties, even if parts from the original content have been omitted before re-publication. The author can indicate which parts can be omitted during certificate generation in a policy. Furthermore, the author can indicate a change in his consent to the content itself or to its re-publication by revoking the content’s certificate.