prosody-modules
527c747711f3
mod_warn_legacy_tls/README.markdown
Software / code / prosody-modules
File
mod_warn_legacy_tls/README.markdown @ 5705:527c747711f3
mod_http_oauth2: Limit revocation to clients own tokens in strict mode
RFC 7009 section 2.1 states:
> The authorization server first validates the client credentials (in
> case of a confidential client) and then verifies whether the token was
> issued to the client making the revocation request. If this
> validation fails, the request is refused and the client is informed of
> the error by the authorization server as described below.
The first part was already covered (in strict mode). This adds the later
part using the hash of client_id recorded in 0860497152af
It still seems weird to me that revoking a leaked token should not be
allowed whoever might have discovered it, as that seems the responsible
thing to do.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Sun, 29 Oct 2023 11:30:49 +0100 |
| parent | 3728:5073bbd86970 |
line wrap: on
line source
TLS 1.0 and TLS 1.1 are about to be obsolete. This module warns clients if they are using those versions, to prepare for disabling them. # Configuration ``` {.lua} modules_enabled = { -- other modules etc "warn_legacy_tls"; } -- This is the default, you can leave it out if you don't wish to -- customise or translate the message sent. -- '%s' will be replaced with the TLS version in use. legacy_tls_warning = [[ Your connection is encrypted using the %s protocol, which has been demonstrated to be insecure and will be disabled soon. Please upgrade your client. ]] ``` ## Options `legacy_tls_warning` : A string. The text of the message sent to clients that use outdated TLS versions. Default as in the above example. `legacy_tls_versions` : Set of TLS versions, defaults to `{ "SSLv3", "TLSv1", "TLSv1.1" }`{.lua}, i.e. TLS \< 1.2.
