Mercurial > prosody-modules
view mod_debug_omemo/README.markdown @ 5682: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 |
| parents | ffddf9b29463 |
| children |
line wrap: on
line source
--- summary: "Generate OMEMO debugging links" labels: - 'Stage-Alpha' ... Introduction ============ This module allows you to view advanced information about OMEMO-encrypted messages, and can be helpful to diagnose decryption problems. It generates a link to itself and adds this link to the plaintext contents of encrypted messages. This will be shown by clients that do not support OMEMO, or are unable to decrypt the message. This module depends on a working HTTP setup in Prosody, and honours the [usual HTTP configuration options](https://prosody.im/doc/http). Configuration ============= There is no configuration for this module, just add it to modules\_enabled as normal. Compatibility ============= ----- ------- 0.11 Hopefully works trunk Works ----- -------