this post was submitted on 29 Jan 2024
100 points (97.2% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54716 readers
219 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Thanks! No, that's exactly what I wanted to do :) I was just wondering if it's okay to have this many random requests, which seems to be fine.
Understood. Any public-facing server will be bombarded by bots. You need to deploy measures to avoid being hacked:
Obviously, there are many other security steps that can be put in place, but firewall and ssh hardening are absolutely mandatory
Thank you, these are great tips!
Being up to date is VERY important. There's a bunch of sites out there that scan the entire internet endlessly and keep information about each IP up to date. For example go here and search your IP.
https://search.censys.io/
When a vulnerability is found, attackers will go to sites like these and look for anything to hack. If you don't update more or less immediately, you're at huge risk.
Other then that, everyone else is right. Being available to the public means you're going to have bots scanning you and sending random trash. The only thing you can do is try and block it (fail2ban) or limit it (block certain countries) but at the end of the day its the software that gets the packets (jellyfin) that you need to trust to be secure and discard random junk.