6 comments

  • idoubtit 34 minutes ago
    That's interesting. I haven't used fail2ban for a long time, but reaction is worth evaluating. Unfortunately, that post does not describe their full configuration. Maybe it's on purpose, so that attackers can't adjust to fit.

    My experience is that modern web scraping had no obvious pattern, since it is proxied through many IPs. The last time a server was failing to handle the pressure, we decided to temporarily ban IPs from some Asian regions. How does the FSF decide to ban an IP?

    Why do they use iptables + ipset instead of nftables? Is there a technical reason or is it just legacy? AFAIK, Nftables is more performant, and IMO simpler. And it has native sets, see https://wiki.nftables.org/wiki-nftables/index.php/Sets

  • Bender 45 minutes ago
    My personal preference is to 'ip route add blackhole ${net}' as it has the lowest CPU overhead and I can add hundreds of thousands of CIDR blocks with no noticeable impact. The only downside is that it won't stop UDP packets from getting to a UDP listener. There will not be a response but the application will still see it. For my TCP daemons it's great.

        grep -m1 -E ^Tot /proc/net/fib_triestat ;ip route | grep -Fc blackhole
        Total size: 56735  kB
        426951
    
    Those 426951 blackhole routes include data-centers, VPS providers, botnets, AI datacenters that ignore robots.txt, search engines, abused CDN's, known bad residential nodes and much more. I still see a few residential proxy bots that do a halfway decent job of pretending to be real people at times but the feds are playing whack-a-mole with them. The bots self report to my silly blog so I can block them elsewhere on systems I might care a little bit about. Happy to share them if anyone is remotely interested.

    I also use a couple generalized rules in nftables raw table that keeps a lot of beyond poorly written bots away including hping3 tcp floods and masscan. My rules to port 443 are stateless. One must not taunt the state table.

  • Magicrafter13 59 minutes ago
    > This software is gay, trans and anticolonialist. If you're uncomfortable with that, please don't use it

    Weird message to include in AGPLv3 licensed software (which explicitly allows people to use software however they like, regardless of their beliefs or feelings).

    • Groxx 56 minutes ago
      You can have preferences while not restricting legal rights.
      • graemep 12 minutes ago
        You can, but if the exact quote in the GP is correct the claim is claiming the software is "gay, trans and anti-colonialist" and asks you not to use it. Why use a license that is designed to be politically neutral and then ask some people not to use it?

        What I can see is a fairly clear indication that they do not want contributions from people whose politics differ from theirs. I would also question whether government funding of a project with political policies about who can participate is appropriate. The political stance is also rooted in a particular culture so is unwelcoming to people from other cultures.

        Of course people can political views and preferences, but they presumably have some aim in mind when making that statement in the README. What is that aim?

        • stonogo 2 minutes ago
          The aim is to reduce the number of users of the software who are uncomfortable with those who are gay, trans, and/or anticolonial, probably because dealing with such people is a heavier burden than the other kind.
  • wasmperson 38 minutes ago
    It's somewhat interesting to see the FSF's approach to this. From what I understand they can't really use something like anubis since they want their websites to be accessible without javascript:

    https://www.gnu.org/philosophy/javascript-trap.html

    Users can't consent to running a page's javascript the way they can consent to running a program they've intentionally downloaded, so it's effectively "non-free" regardless of license.

  • nubinetwork 2 days ago
    > We placed our regular expressions in fail2ban, and found that we were hitting the maximum rules that could be added to UFW firewall rules on our systems which showed degradation around 65,000 rules

    Firewalld had a similar issue up until recently as well.

  • cyanydeez 2 days ago
    are scrapers attackers?

    I get they're DDoS; but take the mask off, and arn't they just the AI monied interests that fund the FSF? and a lot of them are just active inference, eg, the user is trying to ask about something and the AI monied interests setup a web scraper to go and get that data.

    Just seems like no one wants to call out the hand that feeds them in a human centipede that's best described as the torment nexus.

    • nemomarx 1 hour ago
      instead of scraping then, they could pay the fsf for a dump of the site or some API access or something, right? why overload the servers normally.
      • GoblinSlayer 1 hour ago
        That's what commoncrawl does.
        • nemomarx 1 hour ago
          common crawl pays the sites they crawl?
    • kaladin-jasnah 2 days ago
      > AI monied interests that fund the FSF

      Can you elaborate on who these interests are precisely?

      • cyanydeez 2 days ago
        I tried: https://www.fsf.org/patrons; the last FY listed is 2020.
        • kaladin-jasnah 2 days ago
          I'm not entirely sure how those companies are related to "AI-monied" after clicking on their websites.
          • cyanydeez 1 day ago
            the point is i tried to answer and the page is 6 years out of date....
            • socratic_weeb 1 hour ago
              The point is that it is presumed that you must've gotten the info somewhere in order to back up your claims. If not this outdated website, where then?