File

mod_s2s_keysize_policy/README.markdown @ 5571:ca3c2d11823c

mod_pubsub_feeds: Track latest timestamp seen in feeds instead of last poll This should ensure that an entry that has a publish timestmap after the previously oldest post, but before the time of the last poll check, is published to the node. Previously if an entry would be skipped if it was published at 13:00 with a timestamp of 12:30, where the last poll was at 12:45. For feeds that lack a timestamp, it now looks for the first post that is not published, assuming that the feed is in reverse chronological order, then iterates back up from there.
author Kim Alvefur <zash@zash.se>
date Sun, 25 Jun 2023 16:27:55 +0200
parent 1895:101078d9cc27
line wrap: on
line source

---
summary: Distrust servers with too small keys
...

Introduction
============

This module sets the security status of s2s connections to invalid if
their key is too small and their certificate was issued after 2014, per
CA/B Forum guidelines.

Details
=======

Certificate Authorities were no longer allowed to issue certificates
with public keys smaller than 2048 bits (for RSA) after December 31
2013. This module was written to enforce this, as there were some CAs
that were slow to comply. As of 2015, it might not be very relevant
anymore, but still useful for anyone who wants to increase their
security levels.

When a server is determined to have a "too small" key, this module sets
its chain and identity status to "invalid", so Prosody will treat it as
a self-signed certificate istead.

"Too small"
-----------

The definition of "too small" is based on the key type and is taken from
[RFC 4492].

  Type     bits
  ------ ------
  RSA      2048
  DSA      2048
  DH       2048
  EC        233

Compatibility
=============

Works with Prosody 0.9 and later. Requires LuaSec with [support for
inspecting public keys](https://github.com/brunoos/luasec/pull/19).