aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* prosodyctl: Fix spacing in warning messageMatthew Wild2025-04-011-0/+1
|
* mod_roster: Fix shell commands when a component is involved (fixes #1908)Kim Alvefur2025-03-311-1/+1
| | | | | Prevent attempt to load rosters on Components since they do not have users or rosters.
* mod_admin_shell, prosodyctl shell: Report command failure when no password ↵Matthew Wild2025-03-312-2/+12
| | | | entered (fixes #1907)
* util.adminstream: Fix traceback on double-close (fixes #1913)Matthew Wild2025-03-311-2/+2
| | | | | | | | | | | | In some circumstances, particularly with 'opportunistic_writes' and 'fatal_errors' enabled in the epoll backend, the connection may be closed halfway through the session close process (because it contains debug logging, which in the case of the watch:log() command, will trigger a write to the socket). The chosen fix is to cache session.conn in a local variable (we already did this later on, but this pulls it up to the top of the function, which is generally more correct anyway).
* core.portmanager: Restore use of per-host 'ssl' for SNI hosts. Fixes #1915.Kim Alvefur2025-03-291-10/+14
| | | | | | | | | | | This was an unintentional regression, as per-host 'ssl' options became valid in 0.12 when SNI support was added for direct TLS ports. While we encourage most people to use the simpler automatic certificate selection (and it seems most do, given the overlooking of this bug), there are likely always going to be use cases for manually-configured certificates. The issue was introduced in commit 7e9ebdc75ce4 which inadvertently removed the per-host option checking for SNI.
* doap: Add XEP-0333Kim Alvefur2025-03-233-2/+9
|
* doap: Add XEP-0334Kim Alvefur2025-03-233-2/+9
|
* doap: Add XEP-0156 and mod_http_altconnectKim Alvefur2025-03-231-0/+9
|
* mod_http_file_share: Explicitly reject all unsupported rangesKim Alvefur2025-03-231-0/+3
| | | | Fail fast. Otherwise it sends the whole file.
* mod_http_file_share: Fix off by one in Range responseKim Alvefur2025-03-231-2/+3
| | | | See #1914
* mod_storage_sql: Drop legacy index without confirmation to ease upgradesKim Alvefur2025-03-231-10/+6
| | | | | Deleting one index should be safe enough to do without requiring a explicitly upgrading during downtime. People had trouble with this.
* core.usermanager: Fix COMPAT layer for legacy is_admin() functionKim Alvefur2025-03-221-1/+2
| | | | | | Thanks ctrlaltca Fixes #1912
* core.storagemanager: Fix tests by removing an assert that upset luarocksKim Alvefur2025-03-191-1/+1
| | | | Not sure why but this assert() caused a stack overflow in luarocks
* mod_storage_sql: Fix indentationKim Alvefur2025-03-191-28/+28
| | | | Off-by-one in autoindent after `if not success then` since 3ec48555b773
* prosodyctl check: Be more robust against invalid disco_items, and show warningMatthew Wild2025-03-171-4/+32
|
* mod_http_file_share: Improve error reporting by using util.error moreKim Alvefur2025-03-161-9/+30
| | | | | This should pass back the error message as well as the status code to the client.
* Added tag 13.0.0 for changeset a8ad0741632dMatthew Wild2025-03-130-0/+0
|
* CHANGES: 13.0.0 release date13.0.0Matthew Wild2025-03-131-0/+2
|
* CHANGES: Fix 13.0.0 version numberMatthew Wild2025-03-131-1/+1
|
* prosodyctl shell: More reliable detection of REPL/interactive mode (fixes #1895)Matthew Wild2025-03-132-7/+5
|
* mod_admin_shell: Remove outdated help text (fixes #1898)Matthew Wild2025-03-131-7/+2
| | | | | | | | The ! commands have been broken for some time, and we're not going to implement them right now. If we want fancier editing, we can now do that on the client side (with readline and stuff). Also removes mention of telnet!
* prosodyctl check features: Report size limit for HTTP uploadMatthew Wild2025-03-131-3/+21
| | | | This also adds a generic "meta" mechanism where checks can return annotations.
* prosodyctl check features: Add descriptions to featuresMatthew Wild2025-03-131-3/+17
| | | | | Also shuffles mod_pep check to multi-device sync, as I think that's a better fit.
* mod_websocket: Merge session close handling changes from mod_c2s (bug fixes)Matthew Wild2025-03-111-11/+17
| | | | | | | | | | | | | | | | | This should bring some fixes and general robustness that mod_websocket had missed out on. The duplicated code here is not at all ideal. To prevent this happening again, we should figure out how to have the common logic in a single place, while still being able to do the websocket-specific parts that we need. The main known bug that this fixes is that it's possible for a session to get into a non-destroyable state. For example, if we try to session:close() a hibernating session, then session.conn is nil and the function will simply return without doing anything. In the mod_c2s code we already handle this, and just destroy the session. But if a hibernating websocket session is never resumed or becomes non-resumable, it will become immortal! By merging the fix from mod_c2s, the session should now be correctly destroyed.
* mod_c2s: Code formatting changeMatthew Wild2025-03-111-2/+6
| | | | | | Although we do sometimes use single-line if blocks, I'm expanding this one to make it easier to compare with the duplicated (but modified) code in mod_websocket that we plan to de-duplicate one day.
* CHANGES: Add list of new modulesMatthew Wild2025-03-111-0/+9
|
* util.argparse: Fix bug (regression?) in argument parsing with --foo=barMatthew Wild2025-03-112-2/+12
| | | | | | | | | | | | | | | | After recent changes, '--foo bar' was working, but '--foo=bar' was not. The test had a typo (?) (bar != baz) and because util.argparse is not strict by default, the typo was not caught. The typo caused the code to take a different path, and bypassed the buggy handling of --foo=bar options. I've preserved the existing test (typo and all!) because it's still an interesting test, and ensures no unintended behaviour changes compared to the old code. However I've added a new variant of the test, with strict mode enabled and the typo fixed. This test failed due to the bug, and this commit introduces a fix.
* mod_storage_internal: Use UUIDv7 for message idsMatthew Wild2025-03-101-2/+2
| | | | | | This matches what we use for SQL already, so provides some consistency. Client developers prefer sortable ids.
* usermanager: Add info logging for all usermanager account changesMatthew Wild2025-03-101-1/+10
|
* util.sasl: Preserve 'userdata' field between clonesMatthew Wild2025-03-061-3/+8
| | | | | | | | | | | | | | The :clean_clone() method is designed to provide a new cloned SASL handler, to be used when starting a fresh SASL negotiation on an existing connection. The userdata field is currently populated by mod_saslauth with the "read-only" information that the channel binding methods need to do their stuff. When :clean_clone() does not preserve this, it causes tracebacks in the cb profile handlers due to the property being nil. This does mean that SASL handlers should now not be reused (even when cloned) across different connections, if they ever could.
* mod_external_services: Also use TURN REST credential algo for 'turns' ↵Matthew Wild2025-03-011-0/+1
| | | | (thanks moreroid)
* net.server_epoll: Improve readability of DANE noiseKim Alvefur2025-02-271-1/+1
| | | | Serialized Lua is not the most readable form of TLSA records.
* certmanager: Add more debug logging around cert indexingMatthew Wild2025-02-241-2/+6
| | | | | Currently it's not obvious which directories have been indexed (especially when the resulting index is empty), or why certain files have been skipped.
* mod_component: Don't return error reply for errors, fixes #1897Kim Alvefur2025-02-221-1/+3
|
* mod_bosh,mod_websocket: Don't load mod_http_altconnect in global contextKim Alvefur2025-02-222-2/+6
| | | | | | It blocked loading on VirtualHosts since it was already loaded globally Thanks eTaurus
* prosodyctl: check features: stop searching after finding a matching componentMatthew Wild2025-02-221-0/+1
|
* core.configmanager: Pass name and line number in contextKim Alvefur2025-02-221-5/+4
| | | | | | | Delays the string interpolation until the warning is logged, which may slightly lower memory usage. Allows retrieving the filename and line number easily.
* core.configmanager: Fix reporting delayed warnings from global sectionKim Alvefur2025-02-221-10/+5
| | | | | | | | | | | | | | A Credential in the global section would be stored at delayed_warnings["*/secret"], but get("example.com","secret") would look for delayed_warnings["example.com/secret"] Storing the warnings in the config itself has the unfortunate side-effect that the config now contains util.error objects, which may be awkward if something bypasses get(). Should rawget() also do this filtering? getconfig() too? Currently this only affects prosodyctl, so maybe it won't be much of a problem.
* core.configmanager: Remove dependency on 'prosody' global for CredentialKim Alvefur2025-02-222-4/+21
| | | | | Minimizing dependencies on global state is nice, as it makes using configmanager outside of Prosody easier.
* mod_invites: Hide --group flag unless mod_invites_groups is enabledMatthew Wild2025-02-171-1/+6
| | | | | | The WIP groups support is not complete yet, and won't work without extra modules (which are not yet a part of Prosody). For now we hide --group support unless mod_invites_groups (community module) is specified in modules_enabled.
* mod_invites: Fix traceback when no flags passedMatthew Wild2025-02-171-6/+6
|
* mod_invites: Deprecate 'mod_invites generate' in favour of new shell commandsMatthew Wild2025-02-171-108/+61
|
* mod_admin_shell: Improve help listing in non-REPL modeMatthew Wild2025-02-171-2/+36
|
* mod_admin_shell: Fix simple command execution (e.g. help)Matthew Wild2025-02-171-3/+15
|
* mod_admin_shell: Set flag on session when in REPL modeMatthew Wild2025-02-171-0/+4
|
* mod_admin_shell: Improved error handling for shell-invoked commandsMatthew Wild2025-02-171-5/+25
|
* util.argparse: Add strict mode + testsMatthew Wild2025-02-172-9/+56
|
* mod_admin_shell, util.prosodyctl.shell: Process command-line args on ↵Matthew Wild2025-02-172-29/+96
| | | | | | | | | | | | server-side, with argparse support This allow a shell-command to provide a 'flags' field, which will automatically cause the parameters to be fed through argparse. The rationale is to make it easier for more complex commands to be invoked from the command line (`prosodyctl shell foo bar ...`). Until now they were limited to accepting a list of strings, and any complex argument processing was non-standard and awkward to implement.
* util.argparse: Optionally continue processing past positional parametersMatthew Wild2025-02-171-30/+40
|
* util.x509: Per RFC 9525, remove obsolete Common Name checkKim Alvefur2024-02-113-44/+9
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-15 20:51:14 +0000