aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* MUC: Add a test covering basic room creation, messages and destructionKim Alvefur2019-08-311-0/+242
|
* net.server_epoll: Add support for opportunistic writesKim Alvefur2019-08-281-0/+8
| | | | | | | | This tries to flush data to the underlying sockets when receiving writes. This should lead to fewer timer objects being around. On the other hand, this leads to more and smaller writes which may translate to more TCP/IP packets being sent, depending on how the kernel handles this. This trades throughput for lower latency.
* core.certmanager: Remove unused import [luacheck]Kim Alvefur2019-08-251-1/+0
|
* Remove COMPAT with temporary luasec forkKim Alvefur2019-08-254-14/+0
| | | | | The changes in the temporary fork were merged into mainline luasec ca 2013 and included in the 0.5 release in 2014.
* MUC: Simplify nickname refresh loopKim Alvefur2019-08-251-2/+1
| | | | Affiliation data is passed as a loop variable so no need to retrieve it
* core.certmanager: Move EECDH ciphers before EDH in default cipherstringKim Alvefur2019-08-251-1/+1
| | | | | | | | | | | | | | | | | | The original intent of having kEDH before kEECDH was that if a `dhparam` file was specified, this would be interpreted as a preference by the admin for old and well-tested Diffie-Hellman key agreement over newer elliptic curve ones. Otherwise the faster elliptic curve ciphersuites would be preferred. This didn't really work as intended since this affects the ClientHello on outgoing s2s connections, leading to some servers using poorly configured kEDH. With Debian shipping OpenSSL settings that enforce a higher security level, this caused interoperability problems with servers that use DH params smaller than 2048 bits. E.g. jabber.org at the time of this writing has 1024 bit DH params. MattJ says > Curves have won, and OpenSSL is less weird about them now
* mod_storage_internal: Include last text messageKim Alvefur2019-08-231-1/+4
| | | | | | A protocol built on this API now allows showing a list of unread conversations with a counter, ordered by either oldest or newest message, along with the text body itself.
* mod_storage_*: Also include timestmap of first message in :summary APIKim Alvefur2019-08-233-3/+15
| | | | | For completeness along with most recent timestamp. Might be nice to be able to order by oldest unread message.
* mod_storage_*: Include timestamp of latest message in :summary APIKim Alvefur2019-08-233-3/+12
| | | | | | | Clients may want to show a list of conversations ordered by how timestamp of most recent message. The counts allow a badge with unread message counter.
* mod_storage_*: Tweak :summary API to allow future expansion with more fieldsKim Alvefur2019-08-233-9/+15
| | | | Eg might want to include last message, timestamp, chat state or other info.
* mod_auth_internal_hashed: Precompute SCRAM authentication profile name ↵Kim Alvefur2019-08-221-1/+2
| | | | (thanks MattJ)
* mod_auth_internal_hashed: Add support for optionally using SCRAM-SHA-256 ↵Kim Alvefur2019-01-132-6/+8
| | | | | | | instead of SHA-1 This will currently require a hard reset of all passwords back to plain. This will be least painful on new deployments.
* util.sasl.scram: Add support for SCRAM-SHA-256Kim Alvefur2019-01-131-0/+1
|
* util.sasl.scram: Factor out SHA-1 specific getAuthenticationDatabaseSHA1Kim Alvefur2019-01-131-20/+25
| | | | This makes the code more generic, allowing SHA-1 to be replaced
* mod_vcard_legacy: Use PEP nickname if vcard4 data is unavailableKim Alvefur2019-08-221-0/+8
| | | | | | | Last remaining nice feature from mod_profile. Allows setting eg nickname and avatar as completely public while restricting private details in vcard4 to only contacts.
* core.moduleapi: Restructure send_iq method for more atomic cleanupKim Alvefur2019-08-211-16/+23
| | | | | All cleanup in one spot instead of two, and at the end which fits with cleanup happening afterwards.
* core.moduleapi: Uppercase "IQ stanza" for consistencyKim Alvefur2019-08-211-1/+1
| | | | It's written like that elsewhere in the send_iq method
* Merge 0.11->trunkKim Alvefur2019-08-211-0/+1
|\
| * MUC: Advertise XEP-0410 supportKim Alvefur2019-07-301-0/+1
| | | | | | | | Unsure if the feature was in the XEP at the time of 7c1cdf5f9f83
* | Merge mod-installer (2019 GSoC by João Duarte)Matthew Wild2019-08-197-4/+138
|\ \
| * | util/prosodyctl: call_luarocks now sets a directory variable itselfJoão Duarte2019-08-161-1/+2
| | |
| * | util/prosodyctl: Removed the check_flags and execute_command functionJoão Duarte2019-08-161-25/+0
| | |
| * | prosodyctl: Install, remove and list commands now use the call_luarocks functionJoão Duarte2019-08-161-7/+4
| | |
| * | core.configmanager: Removed code related to complement_lua_pathJoão Duarte2019-08-161-2/+0
| | |
| * | util.pluginloader: Added a new path to the variable local_namesJoão Duarte2019-08-161-1/+2
| | |
| * | util.paths: Fixed file termination for package.cpath's extra pathJoão Duarte2019-08-161-1/+1
| | |
| * | util.startup: Changed the way util.paths.complement_lua_path was being accessedJoão Duarte2019-08-161-1/+1
| | |
| * | prosodyctl: Fixed a typoJoão Duarte2019-08-161-1/+1
| | |
| * | util.startup: Reorganized code at setup_plugindirJoão Duarte2019-08-011-3/+3
| | |
| * | util.paths: Refactored a variable, to avoid shadowingJoão Duarte2019-08-011-4/+4
| | |
| * | util.startup: Now calls a function to complement lua's path/cpathJoão Duarte2019-08-011-13/+2
| | |
| * | core.configmanager: Added support to 'complement_lua_path'João Duarte2019-08-011-0/+2
| | |
| * | util.paths: Added the function 'complement_lua_path'João Duarte2019-08-011-0/+16
| | |
| * | util.startup: setup_plugindir now also checks package.cpath for duplicatesJoão Duarte2019-08-011-2/+4
| | |
| * | util.startup: Directly calling lfs.currentdir instead of storing it in a ↵João Duarte2019-08-011-2/+1
| | | | | | | | | | | | local variable
| * | util.startup: Removed/rewrote comments at setup_plugindirJoão Duarte2019-08-011-7/+2
| | |
| * | util.startupt: setup_plugindir now uses lfs.mkdir to check/create directoriesJoão Duarte2019-08-011-4/+1
| | |
| * | util.startupt: I'm now using the resolve_relative_path function from ↵João Duarte2019-08-011-10/+2
| | | | | | | | | | | | util/paths at the setup_plugindir function
| * | util.prosodyctl: Changed a commentJoão Duarte2019-08-011-1/+1
| | |
| * | prosodyctl: Removed the auxiliary command 'enabled_plugins'João Duarte2019-07-311-11/+1
| | |
| * | util.prosodyctl: The check_flags function now considers that a module, if ↵João Duarte2019-07-311-2/+2
| | | | | | | | | | | | given, is specified at the penultimate argument it receives
| * | prosodyctl: The install, remove and list commands now work by calling the ↵João Duarte2019-07-311-33/+7
| | | | | | | | | | | | execute_command function
| * | util.prosodyctl: Added the execute_command functionJoão Duarte2019-07-311-0/+14
| | |
| * | prosodyctl: Rewrote the list command, to make it cleaner and easier to work withJoão Duarte2019-07-311-8/+6
| | |
| * | util.prosodyctl: call_luarocks function is now compatible with the list commandJoão Duarte2019-07-311-1/+5
| | |
| * | prosodyctl: Rewrote the remove command, to make it cleaner and easier to ↵João Duarte2019-07-311-9/+6
| | | | | | | | | | | | work with
| * | util.prosodyctl: Function now differentiates its output, depending if it is ↵João Duarte2019-07-311-1/+7
| | | | | | | | | | | | being called by install or remove
| * | prosodyctl: Rewrote the install command, to make it more cleanerJoão Duarte2019-07-311-14/+9
| | |
| * | util.prosodyctl: Added the call_luarocks functionJoão Duarte2019-07-311-0/+7
| | |
| * | util.prosodyctl: Added the check_flags functionJoão Duarte2019-07-311-1/+12
| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 08:15:28 +0000