aboutsummaryrefslogtreecommitdiffstats
path: root/util
Commit message (Collapse)AuthorAgeFilesLines
* util.prosodyctl.shell: Save readline historyKim Alvefur2020-06-021-0/+7
|
* util.adminstream: Import net.server [luacheck]Matthew Wild2020-06-021-0/+1
|
* util.prosodyctl.shell, util.adminstream: Move connection logic into ↵Matthew Wild2020-06-022-42/+47
| | | | adminstream for easier reuse
* util.prosodyctl.shell: Really fix --socket optionKim Alvefur2020-06-021-1/+3
| | | | | Forgot it stops parsing --foo options at the first argument, so subsequent commands need to parse their own options like this.
* util.prosodyctl.shell: Correct check for --socketKim Alvefur2020-06-021-1/+1
|
* util.human.io: Fix variable name [luacheck]Matthew Wild2020-06-021-1/+1
|
* prosodyctl+util.prosodyctl.*: Start breaking up the ever-growing prosodyctlMatthew Wild2020-06-024-94/+840
|
* util.human.io: New central place for UI helpersMatthew Wild2020-06-021-0/+96
|
* util.prosodyctl.shell: Allow passing path to socket on command lineKim Alvefur2020-06-011-1/+1
| | | | E.g. `prosodyctl shell --socket /path/to/prosody.scok`
* util.prosodyctl.shell: Use same config option as module for socket pathKim Alvefur2020-06-011-1/+2
| | | | | So now if you set it to a custom value, both the client and the server should use it.
* util.prosodyctl.shell: Join socket path with current data directoryKim Alvefur2020-06-011-1/+3
| | | | | | Don't hardcode socket path as it happens to be in a source checkout. Hold on, it should use the same config option as the module!
* mod_admin_shell, mod_admin_telnet, util.prosodyctl.shell: Separate output ↵Matthew Wild2020-06-011-2/+4
| | | | | | from final result Fixes the client pausing for input after output from commands.
* prosodyctl, util.prosodyctl.shell: `prosodyctl shell` - a client to access ↵Matthew Wild2020-06-011-0/+125
| | | | the prosodyctl admin shell
* mod_admin_socket, util.adminstream: New module to manage a local unix domain ↵Matthew Wild2020-06-011-0/+285
| | | | socket for admin functionality
* util.sasl.scram: Mention if clients try PLUS without channel bindingKim Alvefur2020-04-261-2/+6
| | | | This isn't normal, but is it invalid? Likely a client bug in any case.
* util.rsm: Don't convert values to strings that should already be stringsKim Alvefur2020-04-231-4/+4
| | | | Causes util.stanza to throw an error, which helps detect mistakes
* util.rsm: Explicitly serialize numbers in correct formatKim Alvefur2020-04-231-1/+7
|
* util.rsm: Fix passing number as attributeKim Alvefur2020-04-231-1/+6
|
* util.sasl.digest-md5: Remove, obsolete since 2011Kim Alvefur2020-04-142-252/+0
| | | | | | | RFC 6331 lists several problems with this outdated authentication mechanism. The code here was also completely ignored by lint checks and has probably not been used for a long time, as it is incompatible with SCRAM-hashed password storage.
* util.stanza: Add method returning stanza with added indentationKim Alvefur2020-04-121-0/+30
| | | | | Adds indentation and line breaks to stanzas, to make stanzas easier to read for humans.
* util.adhoc: Allow passing dataforms in initial commandKim Alvefur2020-02-261-2/+2
| | | | | This might not be quite legal per XEP-0050, but makes it possible to call simpler commands without keeping state across another roundtrip.
* Merge 0.11->trunkKim Alvefur2020-02-241-1/+1
|\
| * util.datamanager: Fix iterating over "users" (thanks marc0s)Kim Alvefur2020-02-241-1/+1
| | | | | | | | | | | | | | | | | | The 'store' path componend used to be unescaped until 756a2a00e7e7 added escaping to address issues with characters like '/' used in PEP, but with a special case for '_' which was already in common use in 'store' path components. Missed adding this escaping here.
* | util.jwt: Basic JSON Web Token library supporting HS256 tokensKim Alvefur2020-02-241-0/+50
| |
* | util.startup: Break out command line argument parsing into util.argparseKim Alvefur2020-02-192-49/+63
| | | | | | | | | | This will allow using it from other places such as prosodyctl sub-commands and plugins
* | util.startup: expose current process type (prosody/prosodyctl) in the global ↵Matthew Wild2020-01-281-0/+2
| | | | | | | | prosody object
* | util.prosodyctl: Pass command line flag to force daemonization on startKim Alvefur2020-01-261-2/+2
| | | | | | | | | | | | | | Part of the deprecation of the 'daemonize' config option. Further, it is a bit weird to run `prosodyctl start` and get Prosody running in the foreground.
* | Merge 0.11->trunkMatthew Wild2020-01-191-2/+1
|\|
| * util.startup: Ensure prosody.opts exists even when no options provided0.11.5Matthew Wild2020-01-191-1/+1
| |
| * util.startup: Remove accidentally-committed debuggingMatthew Wild2020-01-191-1/+0
| |
* | Merge 0.11->trunkMatthew Wild2020-01-191-37/+39
|\|
| * util.startup: Fix logic to make --config work againMatthew Wild2020-01-191-37/+39
| |
* | Merge 0.11->trunkMatthew Wild2020-01-191-6/+60
|\|
| * prosody/util.startup: Switch to parse_args() for --root and --configMatthew Wild2020-01-191-6/+6
| |
| * util.startup: Add startup step for parsing command-line optionsMatthew Wild2020-01-191-0/+54
| |
* | util.set: Fix equality metamethod in Lua 5.3Kim Alvefur2020-01-151-0/+6
| |
* | util.ip: Fix equality metamethod for Lua 5.3Kim Alvefur2020-01-151-1/+7
| |
* | util.array: Fix equality metamethod in Lua 5.3Kim Alvefur2020-01-151-0/+5
| | | | | | | | | | | | | | | | | | | | | | Lua 5.2 only used the __eq metamethod if both operands have the same __eq, but Lua 5.3 will pick one from either operands that has one as long as both are tables. This results in array() == {} and all sorts of odd behavior, including array() == util.json.null. <MattJ> I think [array() == {}] should have the same semantics as {} == {}
* | util.pubsub: Silence luacheck warnings, leaving notes on future proper fixKim Alvefur2019-12-231-5/+10
| |
* | util.prosodyctl: Silence luacheck warningsKim Alvefur2019-12-231-2/+2
| |
* | util.dependencies: Pass require error to error formatting functionKim Alvefur2019-12-231-10/+11
| | | | | | | | | | | | For future use there. Silences luacheck warnings about unused 'err'
* | util.sql: Handle failure to detect connection encodingKim Alvefur2019-12-231-0/+3
| | | | | | | | Silences a luacheck warning about an unused variable
* | util.mercurial: Ignore an unused error variable [luacheck]Kim Alvefur2019-12-231-1/+1
| |
* | util.startup: Ignore unused errno variable [luacheck]Kim Alvefur2019-12-231-1/+1
| |
* | util.datamanager: Ignore unused 'errno' variable [luacheck]Kim Alvefur2019-12-231-1/+2
| |
* | Merge 0.11->trunkKim Alvefur2019-12-231-4/+10
|\|
| * util.pubsub: Pass subscribers trough a filter callbackKim Alvefur2019-06-061-0/+2
| |
| * util.pubsub: Factor out calling of broadcasterKim Alvefur2019-06-061-4/+8
| | | | | | | | This will simplify doing things along with broadcasting.
* | util.stanza: Accept util.error object to error_replyKim Alvefur2019-12-141-0/+3
| | | | | | | | | | | | | | | | If we're moving towards util.error as the standard error container then this makes sense. This may allow for future extensibility without needing a lot of optional arguments.
* | util.error: Move default for numeric error code to net.http.serverKim Alvefur2019-12-141-1/+1
| | | | | | | | | | | | Stanza errors can also have numbers but these are a legacy thing and rarely used, except in MUC. HTTP errors on the other hand always have a number.