aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | | | | | | mod_time: Remove obsolete XEP-0090 supportKim Alvefur2022-08-153-15/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Deprecated even before Prosody even started, obsolete for over a decade.
| * | | | | | | | | util.datetime: Update Teal interface descriptionKim Alvefur2022-08-171-7/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Integers were required before, now any number should work.
| * | | | | | | | | util.datetime: Remove a lineKim Alvefur2022-08-171-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | No idea why the locals were declared on a line by itself. Perhaps line length considerations? But saving 6 characters in width by adding a whole line with 47 characters seems excessive. This is still within the 150 character limit set by .luacheckrc
| * | | | | | | | | mod_time: Return sub-second precision timestampsKim Alvefur2022-08-141-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Because why not? Who even has this module enabled?
| * | | | | | | | | mod_storage_sql: Drop archive timestamp precision pending schema updateKim Alvefur2022-08-141-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "when" column is an INTEGER which will probably be unhappy about storing higher precision timestamps, so we keep the older behavior for now.
| * | | | | | | | | mod_mam: Store archives with sub-second precision timestampsKim Alvefur2022-08-143-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changes sub-second part of example timestamp to .5 in order to avoid floating point issues. Some clients use timestamps when ordering messages which can lead to messages having the same timestamp ending up in the wrong order. It would be better to preserve the order messages are sent in, which is the order they were stored in.
| * | | | | | | | | util.datetime: Add support for sub-second precision timestampsKim Alvefur2022-08-143-7/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Lua since 5.3 raises a fuss when time functions are handed a number with a fractional part and the underlying C functions are all based on integer seconds without support for more precision.
| * | | | | | | | | util.datetime: Fix argument order in testsKim Alvefur2022-08-141-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The expected value goes first.
| * | | | | | | | | util.signal: Fix name conflict in Teal interface declarationKim Alvefur2022-08-101-4/+4
| | | | | | | | | |
| * | | | | | | | | util.error: Use avoid name conflict in Teal interface declarationKim Alvefur2022-08-101-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Naming things ... Thing or thing_t?
| * | | | | | | | | util.uuid: Fix syntax of Teal interface declaration fileKim Alvefur2022-08-101-1/+1
| | | | | | | | | |
| * | | | | | | | | util.timer: Add Teal interface descriptionKim Alvefur2022-07-241-0/+8
| | | | | | | | | |
| * | | | | | | | | util.termcolours: Add Teal interface descriptionKim Alvefur2022-07-241-0/+7
| | | | | | | | | |
| * | | | | | | | | util.queue: Add Teal interface descriptionKim Alvefur2022-07-241-0/+21
| | | | | | | | | |
| * | | | | | | | | util.logger: Add Teal interface descriptionKim Alvefur2022-07-241-0/+18
| | | | | | | | | |
| * | | | | | | | | util.bitcompat: Add Teal type specificationKim Alvefur2022-06-301-0/+8
| | | | | | | | | |
| * | | | | | | | | util.struct: Add Teal interface description fileKim Alvefur2022-06-151-0/+6
| | | | | | | | | |
| * | | | | | | | | util.table: Add move() to Teal interface description fileKim Alvefur2022-06-151-0/+1
| | | | | | | | | |
| * | | | | | | | | util.set: Add teal type declaration fileKim Alvefur2022-02-161-0/+21
| | | | | | | | | |
| * | | | | | | | | util.serialization: Add Teal type specificationKim Alvefur2021-12-011-0/+33
| | | | | | | | | |
| * | | | | | | | | util.dataforms: Add missing :data() to Teal definitionKim Alvefur2021-11-151-0/+1
| | | | | | | | | |
| * | | | | | | | | util.dataforms: Restructure Teal definition fileKim Alvefur2021-11-151-45/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The PR has been merged and there's no reason not to have nested records and other definitions.
| * | | | | | | | | util.human.io: Add Teal interface definitionKim Alvefur2021-11-101-0/+28
| | | | | | | | | |
| * | | | | | | | | util.promise: Add Teal interface specification fileKim Alvefur2022-07-242-3/+23
| | | | | | | | | |
| * | | | | | | | | teal: add stub util.array teal defsKim Alvefur2022-07-241-0/+9
| | | | | | | | | |
| * | | | | | | | | net.server: Add teal description fileKim Alvefur2022-07-241-0/+65
| | | | | | | | | |
| * | | | | | | | | net.http: Add teal description filesKim Alvefur2022-07-246-0/+190
| | | | | | | | | |
| * | | | | | | | | util.human.units: Specify enum argument to format()Kim Alvefur2021-07-051-1/+4
| | | | | | | | | |
| * | | | | | | | | core.storagemanager: Convert old Typed Lua description file into TealKim Alvefur2021-03-242-68/+74
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Still only a type definition. Typed Lua is no longer maintained. Teal is currently an active project.
| * | | | | | | | | util.hex: Update Teal spec for function rename in a0ff5c438e9dKim Alvefur2022-08-101-0/+2
| | | | | | | | | |
| * | | | | | | | | doap: Update XEP versions for which no code changes appear neededKim Alvefur2022-08-082-14/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | XEP-0004: Partial forms are handled XEP-0045: We're already strict with GC 1.0 XEP-0060: Change in semantics wrt 'pubsub#type', but not in code XEP-0115: No protocol change XEP-0138: Specification moved to Obsolete XEP-0163: Editorial only change XEP-0215: Minor schema change XEP-0280: Editorial change XEP-0297: Had the wrong version number XEP-0106: Note missing piece for version 1.1 XEP-0313: Editorial change XEP-0363: Editorial clarification, no code change required XEP-0380: Registry additions, no code change needed XEP-0384: Not directly supported, only here because people will ask otherwise XEP-0445: Broken out of XEP-0401
| * | | | | | | | | various: Update IETF RFC URLs for tools.ietf.org transitionKim Alvefur2022-08-054-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | See https://www.ietf.org/blog/finalizing-ietf-tools-transition/ Already done in various other places.
| * | | | | | | | | mod_admin_shell: Remove obsolete module:load() argument from 0.8 timeKim Alvefur2022-08-051-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This 'config' argument was removed without explanation in d8dbf569766c
| * | | | | | | | | mod_tls: Record STARTTLS state so it can be shown in ShellKim Alvefur2022-08-022-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This field can be viewed using s2s:show(nil, "... starttls") even without any special support in mod_admin_shell, which can be added later to make it nicer. One can then assume that a TLS connection with an empty / nil starttls field means Direct TLS.
| * | | | | | | | | net.resolvers.basic: Add opt-out argument for DNSSEC security statusKim Alvefur2022-08-021-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This makes explicit which lookups can accept an unsigned response. Insecure (unsigned, as before DNSSEC) A and AAAA records can be used as security would come from TLS, but an insecure TLSA record is worthless.
| * | | | | | | | | Merge 0.12->trunkKim Alvefur2022-07-293-6/+20
| |\ \ \ \ \ \ \ \ \
| * | | | | | | | | | util.sasl.scram: Add 'tls-exporter' as recognised channel binding methodKim Alvefur2022-07-271-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The last missing piece of #1760, otherwise SCRAM-SHA-*-PLUS is not actually advertised.
| * | | | | | | | | | Merge 0.12->trunkKim Alvefur2022-07-273-2/+33
| |\ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | | mod_saslauth: Implement RFC 9266 'tls-exporter' channel binding (#1760)Kim Alvefur2022-06-014-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Brings back SCRAM-SHA-*-PLUS from its hiatus brought on by the earlier channel binding method being undefined for TLS 1.3, and the increasing deployment of TLS 1.3. See 1bfd238e05ad and #1542 Requires future version of LuaSec, once support for this key material export method is merged. See https://github.com/brunoos/luasec/pull/187
| * | | | | | | | | | | util.table: Fix inaccurate commentKim Alvefur2022-07-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Probably a duplicate of the comment next to Lmove, recorded by mistake Lpack can probably be removed at some point in the near future once we are confident it is not used anywhere.
| * | | | | | | | | | | compat: Use table.pack (there since Lua 5.2) over our util.tableKim Alvefur2022-07-115-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added in d278a770eddc avoid having to deal with its absence in Lua 5.1. No longer needed when Lua 5.1 support is dropped.
| * | | | | | | | | | | compat: Remove handling of Lua 5.1 location of 'unpack' functionKim Alvefur2022-07-1117-17/+17
| | | | | | | | | | | |
| * | | | | | | | | | | Merge 0.12->trunkKim Alvefur2022-07-111-1/+1
| |\ \ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | | | luacheck: Set expected globals to Lua 5.4 + compatKim Alvefur2022-07-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Requires luacheck 0.25.0
| * | | | | | | | | | | | Merge 0.12->trunkKim Alvefur2022-07-080-0/+0
| |\ \ \ \ \ \ \ \ \ \ \ \
| * \ \ \ \ \ \ \ \ \ \ \ \ Merge 0.12->trunkKim Alvefur2022-07-080-0/+0
| |\ \ \ \ \ \ \ \ \ \ \ \ \
| * \ \ \ \ \ \ \ \ \ \ \ \ \ Merge 0.12->trunkKim Alvefur2022-07-086-307/+458
| |\ \ \ \ \ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | | | | | | executables: Reject Lua 5.1 earlyKim Alvefur2022-07-022-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Prevents attempting to load libraries that may no longer be found and crashing with a traceback. Platforms like Debian where multiple Lua versions can be installed at the same time and 'lua' pointing to one of the installed interpreters via symlinks, there's the possibility that prosody/prosodyctl may be invoked with Lua 5.1, which will no longer have any of the rest of Prosody libraries available to be require(), and thus would immediately fail with an unfriendly traceback. Checking and aborting early with a friendlier message and reference to more information is better. Part of #1600
| * | | | | | | | | | | | | | | CHANGES: Lua 5.1 support removed (closes #1600)Kim Alvefur2022-07-051-0/+4
| | | | | | | | | | | | | | | |
| * | | | | | | | | | | | | | | util.envload: Remove Lua 5.1 methodKim Alvefur2022-07-051-29/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Part of #1600 Is this module even needed anymore?