• 0 Posts
  • 48 Comments
Joined 1 year ago
cake
Cake day: June 7th, 2023

help-circle



  • Effectively, the other option is passwords, and people are really, really, bad at passwords. Password managers help, but then you just need to compromise the password manager. Strong SSO, backed by hardware, at least makes the attack need to be either physical, or running on a hardware approved by the company. When you mix that with strong execution protections, an EDR, and general policy enforcement and compliance checking, you get protection that beats the pants off 30 different passwords to 30 different sites, or more realistically, 3 passwords to 30 different sites.


  • The modern direction is actually going the other way. Tying identity to hardware, preventing access on unapproved or uncompliant hardware. It has the advantage of allowing biometrics or things like simple pins. In an ideal world, SSO would ensure that every single account, across the many vendors, have these protections, although we are far from a perfect world.






  • Others have given you a good idea, but since you appear to be using Unifi for switch and firewall, o can give you a clear answer: Don’t set vlan on the Synology. Set it as the “Native” VLAN on the switch port going to the Synology.

    Synology can be vlan aware, but you don’t need it. Let the switch do the talking.

    On the Synology I recommend putting it on DHCP while you test. Once it starts getting an IP in the right subnet, you can then switch it to static. Just make sure your gateway is right, putting it wrong will cause the device to not be able to reach outside its own subnet.






  • M365 is doing away with all legacy authentication, do not be surprised if IMAP is completely unusable in the next 12 months. If you simply want to keep a copy of everything, a store and forward SMTP proxy would probably be the solution, so all email going to your domain would hit that first, then send off to M365.




  • The advantage of docker, as I see it for home labs, is keeping things tidy, ensuring compatibility, and easy to manage/backup setup configs, app configs, and app data. It is all very predictable and manageable. I can move my docker compose and data from one host to another in literal seconds. I can, likewise, spin up and down test environments in seconds too. Obviously the whole scaling thing that people love containers for is pointless in a homelab, but many of the things that make it scalable also make it easy to manage.


  • GreyBeard@lemmy.oneto3DPrinting@lemmy.worldPrusa or Bambu?
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    9 months ago

    The Prusa would be a lot more like your Ender. But like your Ender, they aren’t exactly plug and play. That said, they are tried and true work horses. And as another commenter mentioned, very open. Bambu, on the other hand, ships ready to print and from what I hear is reliable and simple. Unfortunately it is much more closed, and you are at the whim of a company that could just decide to kill your printer one day, or take away features with a firmware update.