Basically every local service is accessed via a web interface, and every interface wants a username and password. Assuming none of these services are exposed to the internet, how much effort do you put into security here?
Personally, I didn’t really think about it when I started. I make a half-assed effort at security where I don’t use “admin” or anything obvious as the username, and I use a decent-but-not-industrial password - but I started reusing the u/p as the number of services I’m running grew. I have my browsers remember the u/ps.
Should one go farther than this? And if so, what’s the threat model? Is there an easier way?

  • SchmidtGenetics@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 month ago

    … all it can take is going to a website from a windows device… maybe less, it was literally discovered a couple days ago…

    It’s not like having IPv6 enabled on a windows machine automatically makes it instantly exploitable by anyone out there.

    Yes it actually kinda does, that’s why this exploit is considered the highest priority and critical.

    But sure… downplay it, because we only think servers are at risk…

    Yeesh buddy.