Skip to content
This repository has been archived by the owner on Aug 2, 2020. It is now read-only.

Block Gab's user agent in the server configuration #133

Open
4 tasks
jhaye opened this issue Jul 10, 2019 · 1 comment
Open
4 tasks

Block Gab's user agent in the server configuration #133

jhaye opened this issue Jul 10, 2019 · 1 comment
Labels
A-protection (Affects) protection of users from abusive parties

Comments

@jhaye
Copy link
Contributor

jhaye commented Jul 10, 2019

It has been pointed out by @[email protected] that Gab's fork uses a custom user agent for fetches. This user agent can be blocked by nginx by altering its configuration as follows:

add
if ($http_user_agent ~* (gabsocial)) {
return 403;
}

A few things that need to be done:

  • add this to our docker image by default
  • provide documentation on doing this for manual installs
    • research how to do the same thing with Apache2
  • strategise clear communication on what this will protect people from exactly

While this protection is trivial to bypass, the developer of Gab seems to insist on their own branding of the fork, so I would say this is worth doing.

@jhaye jhaye added the A-protection (Affects) protection of users from abusive parties label Jul 10, 2019
@vitunvuohi
Copy link

A lot of folks are using 444 to immediately close the connection, might be a better option?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-protection (Affects) protection of users from abusive parties
Development

No branches or pull requests

3 participants