v1.23.0: Lyse Hext #1224
Replies: 2 comments 2 replies
-
|
Thanks for the great release ❤️ . I have one regression. Pulling (Docker) containers from my private Forgejo instance yields an 'Unauthorized' with the new version with Traefik and Anubis configured as middleware😒 . Rolling back to 1.22 fixes the issue instantly. Docker login seems to work fine either way. Tests are done on a private network, so I'm at a loss where the issue occurs. Anubis only gives me a "New challenge issued" log. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the release! Lots of work indeed! After the upgrade, I noticed the cute little fox(?) no longer appears. Was it the browser solving it too quickly, or was it no longer present by design? When I curl with the user-agent, I can correctly receive the HTML of the inspecting page. Is there any way that I can see the fox again? I kinda miss him/her/them (not sure). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Sorry this took so long, work has been wiping me out. If you know of any companies that are hiring for someone of my skillset, please let me know.
(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: v1.22.0...v1.23.0
This discussion was created from the release v1.23.0: Lyse Hext.
Beta Was this translation helpful? Give feedback.
All reactions