• 6 Posts
  • 596 Comments
Joined 3 years ago
cake
Cake day: July 6th, 2023

help-circle
  • Do your policy enforcement at the port level, connect the printer with a physical cable, that way even if the printer gets compromised and changes it’s Mac your rules still apply.

    Also setup your network alert system to notify you when a a new driver is available and the printer is behind so you can manually apply security updates.

    1 is fine from the port level

    2 is great, but more brittle

    2.5 only allow incoming connections to the vlan on printer ports, and outgoing mdns

    Depending on your threat model, you might need 3, if the printer is malicious, and printer drivers are also malicious, they can proxy information from the printer through a client device to the internet.






  • In my production systems, and in my home systems, and in my gaming computers, I turn swap off. There’s no good reason to wear out disc writes. In production systems, I’d rather have something fail hard, then get slower and slower and slower falling behind.

    Quite frankly, there’s no good reason to have swap on anymore, memory is huge. Most programs don’t need as much as they use. You can set memory pressure in systemd, telling programs to reduce their usage, and giving them individual hard cutoffs, so something like Prometheus can’t take down your whole system just because it’s got a memory leak.











  • jet@hackertalks.comtoPrivacy@lemmy.ml•My questions regarding many things...
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    7 months ago

    Portable phone: GOS

    Desk phone (wifi only): opionated apps that won’t run on GoS… so basically banking

    Rooting a phone: it changes your security model, so it’s really about the risk reward payoff. Your risk surface area expands greatly.

    In general look at something like qubes, even if you won’t run it, it’s a good thought experiment to see how you would segment things into indivisible risk domains and workflows