Skip to content

forums.debian.net (plethora.d.n) upgrade

  • CPU: As much as possible
  • RAM: As much as possible, but not ludicrous.
  • Disk space: We are at 160 GB using 38GB (after deletion of local stored data)
  • Desired hostname: plethora.debian.net (existing)
  • Public SSH key: On record.

Please provide details as applicable:

What will this instance be used for, who will be the target audience? Debian User Forums.

Who will maintain this service? Will it be team maintained? Same management team, no changes.

What will you use for backups? R-sync.net and offsite on my own cloud,

This request is to address our latest move which gave us more CPU processing power, however which each project action the forums are crawled hard by AI training bots and search engine bots. We have been responding with expanded firewall and other security rules but we are limited in some aspects by the memory we can allot to the firewall vs what has to allocated to the forum itself. As a result of some recent activity from the project the forums are under a botnet/AInet attack that has disabled the service for the actual users of the forum. We would like additional processing and memory to address the blocks needed in place to address this need or help in some regard to our rulesets to accomplish the same goal.

Check-list for Debian.Net Team

  • Select an appropriate platform for the request.
  • Spin up a VM in the appropriate platform.
  • Hetzner Only: Add IPv4 and IPv6 reverse-DNS entries.
  • Add the Debian.Net Team's SSH keys to root's authorized_keys.
  • Set PasswordAuthentication no in sshd_config, restart sshd.
  • Add an account for the requester adduser --disabled-password USER.
  • Grant sudo access to the requester adduser USER sudo.
  • Unset the user's password, so they can set it themselves: passwd -d USER
  • Add the requester's SSH keys to their account's authorized_keys.
  • Provide IPv4 and IPv6 addresses in a comment, so the requester can create DNS records.
  • Provide the host SSH fingerprint ssh-keygen -l -f /etc/ssh/ssh_host_ed25519_key in a comment.
  • Add the instance to the infrastructure repo