• 0 Posts
  • 12 Comments
Joined 3 years ago
cake
Cake day: June 15th, 2023

help-circle
  • Also, I’ve never been able to understand how something exposed to the entire internet (a WG server) is considered more secure than something that only connects peers privately to each other.

    The attack surfaces are nothing alike.

    Even if you limit access to WG with IP blocking there’s still no comparison to something you can’t access at all from outside.


  • With Migadu you can send email as anything you want @yourdomain, as long as you use the correct credentials (user+password) for SMTP. You don’t have to set up anything in advance, you just modify your “From” in the mail client. The “From” addresses don’t have to bear any relation to any alias or pattern or existing mailbox, just have to be @ the domain associated with the SMTP login. It’s entirely your problem if the address doesn’t make sense and whether the recipient will be able to reply.

    There are mail clients that know how to work with this and let you set up multiple sender “identities” that are basically bookmarked “From” addresses. Migadu’s webmail also has this feature (not sure what webmail app it is, HTML source code says “SnappyMail”). But as long as the email client lets you edit the “From” field you can always change this on the fly.




  • Migadu will probably fit all your requirements.

    Services that support multi-user accounts, where I can be the admin and manage our domains.

    Migadu pricing only cares about storage space used and emails sent/received. You can have any number of domains or mailboxes or accounts otherwise, and there’s a lot of features and flexibility for the admin.

    Ability to assign domains for specific user accounts.

    Not sure how exactly you mean this but it’s probably more flexible than you intend. You can create any number of mail accounts under any of the domains you add to it.

    Ease of use for users to create aliases on the fly within the password manager.

    They have a thing called “pattern rewrites” that could be better called “wildcard aliases”. Basically you can have aliases with both variable and fixed parts. For example “shop-*@example.com” will receive email sent to “shop-amazon@” and “shop-walmart@” but not to “amazon@”. It’s a sort of catch-all’s, but mitigates some of the downsides of an actual catch-all because outsiders can’t guess what’s your fixed part of the alias.

    They also have regular aliases, domain aliases, catch-all’s and some other stuff.

    I typically use those wildcard things for all my needs.

    European hosted and privacy focused, with good encryption.

    They’re Swiss-based and committed to privacy.

    Regarding encryption, if that’s a deal-breaker to you I’d urge you to reconsider. Encryption for email-at-rest is a gimmick. There’s only a handful of providers that even attempt it, because it’s nonsense, but if spinned right it appeals to the public. You will get away from Proton only to get locked down by Tuta or… actually I don’t remember if there was a 3rd.

    Preferably open source clients.

    You don’t want open source clients, you want standard protocols (IMAP and SMTP). You can use any standard mail client with those protocols, both open- and non-open-source clients.

    The problem with “encrypted email” is that it doesn’t work without putting it through non-standard protocols, which lead directly to lock-in. So they’ve spinned it so that you need a “special client” to work with it. But whether Proton’s special client is open-source or not is irrelevant, because they can close down their non-standard protocol at any given moment and close source the client and your mailbox becomes their prisoner.

    All you need is a provider with regular IMAP and SMTP, and when a provider starts acting up you can switch to another one with regular IMAP and SMTP as fast as your domain(s)’ DNS can propagate.





  • Any EU/Swiss-based provider that takes their job seriously, really. Here’s a starting point.

    Proton’s encryption has always been more a publicity stunt than anything. A service that’s really committed to privacy shows it in their values and the way they act, not with technological gimmicks.

    All that Proton’s encryption has really accomplished is that their services are one step away from complete customer lock-in: if they discontinue their “bridge” connectors tomorrow and force you to use their website and mobile app, and you haven’t backed up your email elsewhere, you’re fucked.

    Migrating your email service to another provider should normally take one hour, provided you use your own domain(s) and back up your mailboxes regularly over IMAP to your own storage. Then it’s just a matter of changing some DNS records and waiting for them to propagate.

    So call me paranoid but I’ll never use a provider that doesn’t offer standard IMAP and SMTP access to the mailbox.


  • Google started as a search engine and ad company, and has since reinvented itself with investment in new areas like photos, email, Android, etc.

    There’s really no point in comparing Google to Yahoo. Google actually developed a solid strategy fairly early on, which involved (1) collecting data from any source possible (all their services are designed around collecting data), (2) selling that data to advertisers, and (3) (very important) creating and owning platforms (Android, Chrome, Youtube, Pixel, GCP etc.) that allow them to not depend on anybody else.



  • Why not use PHP hardened (distroless) images as a base for the final image?

    Why build your own images at all? I’m not sure I understood what advantage that gives you.

    Harbor looks interesting but that install procedure is ridiculous. Why would I run an installer script just to pull docker images, just give me a compose file ffs. The only way I’d ever consider it is inside an LXC container or a VM.

    Also, it sounds like they’ve never heard of a reverse proxy and don’t know you can do TLS that way? That does not inspire confidence.