On linux, passwords are usually stored system-wide, unencrypted for all users to access. There’s the option (at least on NetworkManager) to store them user-side using any secret service (KWallet, gnome-keyring, KeePassXC). The problem with this, at least with KeePassXC, is that I have to unlock the vault every time to connect to wifi, and it gets pretty annoying. I know there’s always the security over convenience but wondering if its really necessary, or I’m possibly doing it wrong.
after considering some other things it’s actually just fine, unless theres things like username/password networks that another user of the device that should be using their own login
I honestly do not store that password into any PW manager.
I mean, I’m also most of the time just wired.
But I’d recommend not pushing the boundaries so that everything in your life needs to go through a manager, there are quite a lot of diminishing returns for every day things.
It is quite unlikely that somebody comes next to your door and brute-forces into your WiFi.
And I mean, if they do: having yours stored in a manager doesn’t really make it anyhow secure.
Consider using a big key for some WPA3 Personal and rotating it every few months (weeks?) if really concerned.
Otherwise, you can give WPA3 Enterprise a try but that will induce the need for a RADIUS server, you’ll see which one fits your use case.
I thought we retired the idea of changing passwords on a schedule. Most people would get lazy and make them easier, and you just end up cheating yourself. If you’re not one of those people, good for you but my point still stands