• 4 Posts
  • 27 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle





  • Old hardware is awesome to reuse most of the time but it’s not nearly as efficient as our hardware today.

    It’s probably good to just properly recycle the old gear and spend $200 on a mini-PC from Amazon that has three times the power all while using less electricity.

    I usually completely tear down old equipment into is raw materials, the best I can. It’s less likely to be shipped off to another country for uncontrolled destruction and I get more money back for the materials.



  • I will echo many others here: It’s going to be rough getting good deliveries. While you are planning on running a proxy, that is basically the same as running an open port where your server is. While it may seem to be a good idea to send email from a random AWS address, it really isn’t. Unless you are behind an IP that is specifically trusted as an email source, your traffic has a higher probability of getting dropped. (Many dynamic IP ranges for home internet connections are marked as invalid or untrusted sources, btw.)

    Additionally, email servers are a hot commodity, especially if they are not blocked (yet) by the larger filter providers. All it takes is one or two reports or a poorly configured firewall/IDS to auto-trigger a submission of your IP address as “bad”. By hot commodity, I mean you are going to get fuck tons of vulnerability scans. It’s not the end of the world, but it’s super annoying.

    If I was operating as a Jr. Security Analyst again and saw and sus traffic coming from your address, I would submit a block and not think twice about it. Hell, most of those types of blocks are automated anyway.

    However, if you do set one up and all is golden, great! It’s worth the experience but something I won’t ever do again. (Yes I did run my own email server before.)


  • Rate limiting only goes so far. 10 requests for a 1 second operation is the same thing as 1 request for a 10 second operation. Any CDN, like CloudFlare, can’t do too much about web requests that are super taxing on the database.

    The bot nets that are doing this can be worse than a hydra. If you block one bot, several more pop up to take over where the other left off. Even worse, the requests that the bots are making are legitimate. If you start throttling the specific requests that are too taxing, you are likely going to cause issues for legitimate users that need the same data.

    Additionally, the number of NAT’ed egress IP addresses are much higher than you might think. Blocking just one IP address could mean that you are blocking thousands of users behind that address.

    Sometimes, the best option is to absorb the traffic and ensure that your application is running extremely efficiently.

    This is a complex problem, for sure.