Errar es humano. Propagar errores automáticamente es #devops

https://vsis.online/

  • 2 posts
  • 29 comments
Joined 3 years ago
Cake day: June 18th, 2023
  • Wait.

    Does Portainer ask your email? I haven’t used it in years. I though it was just a container that you run, with mounted docker socket, and that’s it.

    Is it now doing some “telemetry” and sending user data, like email, to their servers? If so, I’m glad I’m not using that anymore.

I want a centralized way to manage keys and secrets. And some service users with little privileges over a subset of the secrets. Ideally, a service user only should be able to read its own subset of secrets. So, let’s say, if a container gets pwned it will only read its secrets and no more. It should be FOSS and self-hostable.

And a beautiful nice-to-have feature would be access log, to know who read what and when.

My only experience with something similar is Hashicorp Vault, but I don’t want to be near any Hashicorp stuff ever again.

Do you know a FOSS alternative to Vault?

  • If your comments have been federated to other instances, they will be there until they are deleted locally. If someone clicks on your user profile, they will get a DNS error if the domain is no longer there. Images in the comments pointing to you instance will be broken too. Nothing terrible actually happens.

    Migrating accounts a la Mastodon is not happening soon in Lemmy.

    My advice is: Go on and save some money.

  • Some security tips:

    Firewall should block everything by default, and you start allowing incoming and outgoing connections when you need them or if something fails.

    Disable passwords and root access in ssh daemon.

    Use fail2ban or something similar to block bots failing to log-in.

    Use random long passwords for everything (eg: like databases). And put then in a password manager. If you can remember the database password, it’s not strong enough. If you can remember the admin password for a public web service, it’s weak.

    Don’t repeat the passwords. Everything should have its own random long password.

    .env files and files with secrets should be readable only by its service user. Chmod them to 400.

    Monitor logs from time to time to see if something funny is happening.

  • Random ports are easy to discover and there are tools to discover what service is behind a port.

    It’s annoying for the legitimate user and easy to bypass by an actual attacker.

    Also, if you use a random port above 1024 it could be a security issue since any user could star listening if the legitimate process crashes.

    See this

Hello. Let’s say I want to selfhost an email server (smtp + imap) that only will be used to receive email.

I only will send email internally (from my domain to my domain) and receive from 3rd parties.

Should I setup DKIM, DMARC, SPF and reverse IP lookup?

To be honest, I’m having a bit of hard time understanding the madness of email authentication. So I can’t figure it out by myself if those mechanisms are needed in my case.

I haven’t deployed anything, but probably will use Stalwart. It looks like it’s easy to deploy. Is there any other beginner-friendly email service I should read about?

Thanks!

  • I don’t know any product that matches your requirements.

    If I had to deal with that today I’d buy a rasberry pi, a USB sim card dongle and some raspberry hat with GPS receiver.

    You can write a small API that listens to the raspberries, who sends periodically their positions, and save it to a database.

    But it’s a quite large project. There’s a lot of aspects to consider. The GUI, security, batteries, and a way to attach it to an animal without being lost or destroyed.

    Sorry for not giving a useful answer lol. If you come out with an actual solution I’ll be glad to hear it, so I can track my cats in case they get lost.