Mercurial > prosody-modules

view mod_cloud_notify_extensions/README.md @ 6319:04c3273cb81f

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_auth_cyrus: Add empty 'profile' table to SASL handler objects This is for compatibility with Prosody's built-in util.sasl objects. A SASL profile table usually includes methods supported by the backend, which can be used by SASL mechanism handlers to perform operations (such as testing the password). It also optionally contains a 'cb' field with channel binding method handlers. The Cyrus backend doesn't support channel binding, and doesn't have the same concept of auth backend methods (it handles all that internally, and Prosody has no insight or control over it). Thus, we create an empty profile which informs Prosody that the SASL handler does not support any of the auth or channel binding methods. Some features will not work, but they didn't work anyway. This just makes it explicit. This fixes a traceback in mod_sasl2_fast, which expected SASL handlers to always contain a 'profile' field.
author Matthew Wild <mwild1@gmail.com>
date Thu, 04 Sep 2025 10:14:46 +0100
parents fe081789f7b5
children
line wrap: on
line source

---
summary: "Tigase custom push extensions for iOS"
labels:
- 'Stage-Beta'
rockspec:
  dependencies:
	- mod_cloud_notify_encrypted
	- mod_cloud_notify_priority_tag
	- mod_cloud_notify_filters
...

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

This is a meta-module that simply enables all the modules required to support
Siskin or Snikket iOS on a Prosody server.

These are currently:

- [mod_cloud_notify_encrypted]
- [mod_cloud_notify_priority_tag]
- [mod_cloud_notify_filters]

See the individual module pages for more details. In particular,
mod_cloud_notify_encrypted depends on
[luaossl](http://25thandclement.com/~william/projects/luaossl.html), which
must be installed. It is available in Debian via apt as
[`lua-luaossl`](https://tracker.debian.org/pkg/lua-luaossl) or via
`luarocks install luaossl`.

Note: On MUC services you should also load mod_muc_offline_delivery directly
under the MUC component in your config file, that is not handled by this
module.

Configuration
=============

There is no configuration for this module, just add it to
modules\_enabled as normal.

# Compatibility

  ------- -------------
  0.12    Works
  0.11    Should work
  trunk   Works
  ------- -------------