anubis 1.23.0 #251906
Open
anubis 1.23.0 #251906
+3
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
go
|
daeho-ro
force-pushed
the
bump-anubis-1.23.0
branch
from
90c8ff8 to
bc6b13c
Compare
|
chenrui333
added
the
help wanted
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created by
brew bumpCreated with
brew bump-formula-pr.release notes
(data)/meta/default-config.yamlfor importing the entire default configuration at once.-custom-real-ip-headerflag to get the original request IP from a different header thanx-real-ip.contentLengthvariable to bot expressions.COOKIE_SAME_SITE_MODEto force anubis cookies SameSite value, and downgrade automatically fromNonetoLaxif cookie is insecure.SLOG_LEVEL,COOKIE_PREFIX,FORCED_LANGUAGE, andTARGET_DISABLE_KEEPALIVE(#1086).robots2policyto properly group consecutive user agents intoany:instead of only processing the last one (#925).fastalgorithm prefer purejs when running in an insecure context.s3apistorage backend to allow Anubis to use S3 API compatible object storage as its storage backend.techaro.lol-anubis-authinstead oftecharo.lol-anubis-auth-auth.cmd/containerbuildsupport commas for separating elements of the--docker-tagsargument as well as newlines.DIFFICULTY_IN_JWToption, which allows one to add thedifficultyfield in the JWT claims which indicates the difficulty of the token (#1063).targetSNIto special keyword 'auto' to indicate that it should be automatically set to the request Host name (424).Potentially breaking changes
Multiple checks at once has and-like semantics instead of or-like semantics
Anubis lets you stack multiple checks at once with blocks like this:
Previously, this only returned ALLOW if any one of the conditions matched. This behaviour has changed to only return ALLOW if all of the conditions match. I expect this to have some issues with user configs, however this fix is grave enough that it's worth the risk of breaking configs. If this bites you, please let me know so we can make an escape hatch.
Better error messages
In order to make it easier for legitimate clients to debug issues with their browser configuration and Anubis, Anubis will emit internal error detail in base 64 so that administrators can chase down issues. Future versions of this may also include a variant that encrypts the error detail messages.
Bug Fixes
Sometimes the enhanced temporal assurance in #1038 and #1068 could backfire because Chromium and its ilk randomize the amount of time they wait in order to avoid a timing side channel attack. This has been fixed by both increasing the amount of time a client has to wait for the metarefresh and preact challenges as well as making the server side logic more permissive.
What's Changed
New Contributors
Full Changelog: TecharoHQ/anubis@v1.22.0...v1.23.0
View the full release notes at https://github.com/TecharoHQ/anubis/releases/tag/v1.23.0.