| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This should speed up repeated requests to the same site by keeping their
connections around and sending more requests on them.
Sending multiple requests at the same time is not supported, instead a
request started while another to the same authority is in progress would
open a new one and the first one to complete would go back in the pool.
This could be investigated in the future.
Some http servers limit the number of requests per connection and this
is not tested and could cause one request to fail, but hopefully it will
close the connection and prevent it from being reused.
|
| |
| |
| |
| |
| | |
Potentially allows sorting on those directly as they will be in
increasing order.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Allows sorting by id as a substitute for sorting by timestamp since it
has the timestamp in the encoded in the first part, and only things that
happen extremely close together may get out of order by such a sort,
which might not matter.
From draft-ietf-uuidrev-rfc4122bis formerly draft-peabody-dispatch-new-uuid-format
|
| |
| |
| |
| | |
modules_enabled (thanks aab and Menel)
|
| |
| |
| |
| | |
Security considerations added, no protocol changes.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Previously the whole grant was deleted if it found one expired toke,
which was not indented.
|
| | |
|
| |
| |
| |
| | |
initialization
|
| |
| |
| |
| | |
Not the prosodyctl check dane I wanted to make but a start.
|
| |
| |
| |
| |
| |
| |
| | |
One small refactor but one huge step in the right direction
Mostly because adding another check would make the line checking for a
valid check exceed the column limit.
|
| |
| |
| |
| | |
Does this make it clearer what is going on?
|
| | |
|
| |
| |
| |
| | |
Simplifies configuration, only one already existing boolean to flip.
|
| |
| |
| |
| |
| | |
Complements the DANE support for outgoing connections included in
net.connect
|
| | |
|
| |
| |
| |
| |
| |
| | |
* mod_authz_internal adds account_roles
* mod_cron has its state
* mod_smacks also has some non-critical state
|
| |
| |
| |
| | |
Everything supports SNI today, so this is not useful information.
|
| |
| |
| |
| |
| | |
This matches what mod_c2s does, and fixes a traceback in mod_sasl2_fast when
used with BOSH (that module tries to use event.stream.from).
|
|\| |
|
| |
| |
| |
| | |
A typo should not result in ending up with "legacy"
|
| |
| |
| |
| | |
(thanks tmolitor)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This channel binding method is now enabled when a hash is manually set in the
config, or it attempts to discover the hash automatically if the value is the
special string "auto".
A related change to mod_c2s prevents complicated certificate lookups in the
client connection hot path - this work now happens only when this channel
binding method is used. I'm not aware of anything else that uses ssl_cfg (vs
ssl_ctx).
Rationale for disabling by default:
- Minor performance impact in automatic cert detection
- This method is weak against a leaked/stolen private key (other methods such
as 'tls-exporter' would not be compromised in such a case)
Rationale for keeping the implementation:
- For some deployments, this may be the only method available (e.g. due to
TLS offloading in another process/server).
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Some of the new roles don't quite fit nicely into 4 characters
(excluding ellipsis). Given the ability to dynamically add additional
roles from the config and possibly from modules, it seems better to just
make it a relative size since we can't know how long they will be.
|
| |
| |
| |
| | |
Explicit > implicit
|
| | |
|
| |
| |
| |
| | |
Requested feature for many modules, notably MAM and file sharing.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
MattJ contributed new APIs for retrieving the actually used certificate
and chain to LuaSec, which are not in a release at the time of this
commit.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This originally used a WIP implementation of cert:sigalg(), a method to
retrieve certificate signature algorithm, but it was never submitted
upstream. https://github.com/Zash/luasec/tree/zash/sigalg
cert:getsignaturename() was merged in
https://github.com/brunoos/luasec/commit/de393417b7c7566caf1e0a0ad54132942ac4f049
XEP-0440 v0.3.0 made implementing tls-server-end-point a MUST
|
| |
| |
| |
| |
| |
| |
| |
| | |
Since this channel binding method is said to enable TLS offloading then
you need tell Prosody the hash (or the full cert), so this seems like a
good start.
Support is RECOMMENDED in XEP-0440 version 0.2
|
| | |
|
| |
| |
| |
| | |
Ensures the periodic cleanup really does remove expired tokens.
|
| |
| |
| |
| | |
This should ensure expired grants eventually disappear.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Generally it is expected that a grant would have at least one token as
long as the grant is in active use.
Refresh tokens issued by mod_http_oauth2 have a lifetime of one week by
default, so the idea here is that if that refresh token expired and
another week goes by without the grant being used, then the whole grant
can be removed.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Silence warning for using this introduced in 9c62ffbdf2ae
|