view mod_sift/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 d3231a4d6a60
children
line wrap: on
line source

---
labels:
- 'Stage-Alpha'
summary: 'XEP-0273: Stanza Interception and Filtering Technology'
...

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

[SIFT][XEP-0273] is a technology to allow clients to filter incoming
traffic on the server. This helps save bandwidth, etc.

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

  ----- -------
  0.7   Works
  ----- -------

Quirks
======

This implementation is a work in progress.

-   Stanzas to full JIDs get sifted correctly
-   Stanzas to bare JIDs are currently allowed/disallowed for all
    resources as a whole, and not for individual resources
-   Presence is only sent to available resources, and probes are not
    sent for unavailable reasources
-   This module currently does not interact with offline messages
    (filtered messages are dropped with an error reply)
-   Not tested with privacy lists