anubis: "invalid response." after "Success!" in Chromium
Hi, thank you very much for Anubis!
I’ve just set it up for two websites on the same server:
- https://wiki.dlang.org/ - works perfectly.
- https://dsource.org/ :
- In Firefox: works perfectly.
- In Chomium: In a new private window, I see, in quick succession:
- “Making sure you’re not a bot”
- “Success!”
- “Oh noes!” / “invalid response”
- On this page, nothing happens if I click “Try again”, but clicking “Go home” results in a “Success!” and successful website load.
Any idea what could be the problem?
Installed from anubis_1.18.0_amd64.deb.
Browser versions:
- Firefox 136.0.3
- Chromium 134.0.6998.165
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 23 (8 by maintainers)
Commits related to this issue
- fix(lib): fix invalid response after success in Chrome Closes #564 This one is really dumb. Take a seat and listen to my tale of woe. While @victorvalenca was working on #693 we ran into a strange ... — committed to TecharoHQ/anubis by Xe a year ago
- fix(lib): fix invalid response after success in Chrome (#711) Closes #564 This one is really dumb. Take a seat and listen to my tale of woe. While @victorvalenca was working on #693 we ran into a s... — committed to Mu-L/anubis by Xe a year ago
- fix(web/main): remove the success interstitial I'm gonna be totally honest here, I'm still not sure why #564 is still an issue. This is really confusing and I'm going to totally throw out how Anubis ... — committed to TecharoHQ/anubis by Xe a year ago
- fix(web/main): remove the success interstitial I'm gonna be totally honest here, I'm still not sure why #564 is still an issue. This is really confusing and I'm going to totally throw out how Anubis ... — committed to TecharoHQ/anubis by Xe a year ago
- fix(web/main): remove the success interstitial (#745) I'm gonna be totally honest here, I'm still not sure why #564 is still an issue. This is really confusing and I'm going to totally throw out how ... — committed to TecharoHQ/anubis by Xe a year ago
Okay, I have a complete rewrite of the challenge creation flow in #749. I think my core assumptions about browsers work with regards to how challenges were created is fundamentally incorrect. I assumed that my challenge creation method was idempotent, or that a single client hitting that route at time t0 to get string s0 would also get string s0 when hitting that route at time t1. This is apparently false and instead of fighting windmills trying to figure out why, I changed this to use a completely different flow.
Now Anubis generates a new challenge string based on 256 bytes of cryptographically random data. Anubis stores metadata about challenges (including the challenge string) in a Store. Right now the only Store is a simple in-memory data structure based on decaymap. Before that PR merges, I will add storage backends for the following:
In addition, I think part of the reason this is stinging so bad is that there is a core UX flaw with this approach: the “success” screen doesn’t actually mean “server accepted challenge”, it means “client found a solution”. I made #745 to remove that as a stopgap.
Hopefully this will stop the bleeding.
Thank you for bearing with me.
The root cause has been fixed in #711. This fix will be out in v1.20.0 soon.
I think I have finally fixed this bug for good in #749.
If you use Anubis via Docker, please update to
ghcr.io/techarohq/anubis:main. Please be sure to add a docker volume for persistent storage on the disk mounted to/dataand add the following to your configuration/policy file:If you use Docker compose, the end result could look like this:
If this fixes the issue, I’m going to tag Anubis v1.21.0 this weekend. If not, comment here with information so we can all suffer together.
I am sorry to report that the problem seems to be still there, chrome (ipv6) and firefox (ipv4)