| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
When the reason is reported as an util.error object the `reason` field
is empty and the reason text should be extacted from the error object.
|
|
|
|
| |
Probably because autocomplete.
|
|
|
|
| |
(thanks Ge0rG)
|
|
|
|
| |
Causes util.stanza to throw an error, which helps detect mistakes
|
| |
|
|
|
|
|
|
|
|
| |
The 'max' 'count' and 'index' fields are integers and should be encoded
as such on the wire.
Care needs to be taken because tostring(1.0) in Lua 5.3+ returns to "1.0"
while in previous Lua versions it would return "1".
|
| |
|
|
|
|
| |
Based on examples from XEP-0059
|
| |
|
|\ |
|
| |
| |
| |
| | |
Logic using full vs bare JID addressing may return in the future.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent was to not store MUC groupchat messages, which are sent from
the MUC to local full JIDs, while allowing for potential future
account based group chat. However, since this function handles messages
in both directions and outgoing MUC messages are sent to the bare room
JID, those were stored.
|
| |
| |
| |
| |
| |
| |
| |
| | |
In Lua 5.3 difftime() takes integers as argument but returns a float,
and then tostring() serializes it with a decimal point. This violates
XEP-0012.
Like #1536
|
| | |
|
| |
| |
| |
| | |
Somehow it got SHA1's 20 byte output instead of the proper 32 = 256/8
|
| | |
|
| |
| |
| |
| |
| | |
Since these XEPs are subject to change we may need come back and double
check these in the future.
|
| |
| |
| |
| |
| | |
Makes it possible to learn of delivery failure even if it came bouncing
back while you were offline.
|
| | |
|
| |
| |
| |
| |
| | |
no-store is used in an example in XEP-0313, so obviously this is the
preferred hint
|
| |
| |
| |
| | |
If it is with a body then it execution does not get this far
|
| | |
|
| |
| |
| |
| |
| |
| | |
The intent is to capture errors to stanzas sent by the local user, so
that they can see why a message failed to be delivered even if the error
came after they went offline.
|
| |
| |
| |
| | |
Happy now Ge0rG?
|
| |
| |
| |
| | |
Mostly just lifted from mod_csi_simple
|
| |
| |
| |
| | |
Improved readability and early returns definite yes/no answer.
|
| |
| |
| |
| |
| | |
This is based on code in mod_csi_simple and aiming towards being more
flexible and maintainable than a couple of tests for when not to store.
|
| |
| |
| |
| |
| | |
Logging of 'why not' is already done. Why not both? Will make more sense
when the rules evolve a bit.
|
| |
| |
| |
| |
| | |
Meant to improve readability and ease further improvements to this
algorithm.
|
| |
| |
| |
| |
| | |
Both mediated invites defined by XEP-0045: Multi-User Chat and direct
invites defined by XEP-0249: Direct MUC Invitations
|
| |
| |
| |
| | |
When run on Lua 5.3 produces an issue similar to #1536
|
| |
| |
| |
| |
| | |
Once the Prosody is up, who cares when it comes down?
That's not my department, says scanison.
|
| |
| |
| |
| | |
The passage of time does not need test coverage, just look in a mirror.
|
| |
| |
| |
| | |
Why was this module enabled in the config for tests if it wasn't tested?
|
|\ \
| |/
|/| |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
I guess this contained the old per-store migrators
|
| |
| |
| |
| | |
Same way as with the prosody and prosodyctl executables
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(fixes #1513)
Backport of 94e341dee51c
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
|
| |
| |
| |
| | |
Backport of 88be11e9f9b9
|
| |
| |
| |
| | |
Oversight in 955e54e451dc when this was added.
|
| |
| |
| |
| | |
Improves readability, easier to see structure.
|