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

help-circle

  • I had a similar journey and at some point settled for Debian.

    I know, everyone around here will tell you how basic that is and how much program versions lag behind sometimes, but I have come to the conclusion that this really doesn’t bother me on daily use.

    The main wow moment was, when the I noticed my system was running for 5 years and nothing ever broke.

    Sure, I sometimes miss the AUR or some of the bells and whistles off bleeding edge distros, but in the end I want my main daily driver as a tool to other stuff, not a project to constantly put effort in.

    The beauty of Debian is, its reliable AF, everything you got working once stays working, in 99,99% of cases even with a major version change, its the best documented and tested system and it does everything I need and more.

    Plus with KDE plasma and all the native programs, like kdeconnect, kdenlive, kget etc I dont miss out on convinience. (Sure I could still use them on other distros, but I like how it is integrated into a good user experience with the option to tweak everything but without the need to do so)

    The main down site imho is that some advanced things which may work in a hacky and time consuming way on arch just will not work on Debian at all, but I seldom have such moments and its a small price to pay for a system that’s just won’t brake from where I stand.


  • Maybe I am not informed enough, i don’t exactly know if i missed something , but i did what i would do under microslop, I reset to factory keys I enable secure boot in user mode and I boot.

    When checking in the KDE security info, secure boot isn’t enabled.

    I asked lenovo support on how to do it (along with how to do an bios update under Debian) and the just replied there is no support for Linux. For either of those for my model and disabled the option to get support from a real human for my serial number.

    Maybe I would have needed to “enroll my keys”, I did not do that, mainly because I didn’t knew I needed to, and still dont know where to get my keys from and how to enroll them. Maybe you could enlighten me.

    Side rant: That I had to enter my full details including age and address and my serial number to even be able to get a support ticket is unbelievable imho

    My device isn’t included in the fwupd.





  • Okay, maybe I’m misunderstanding something, but my thinking goes like this:

    1. A personal computer I dont control, which is infected logs onto the wifi network of family A. This device has no permissions (based on its ip), so it can’t access the shared media server.
    2. This device could spoof a Mac address of a device with permissions on the same network through brute force, so it gets their IP along with its permission (access to media server)
    3. It could at least do bad actions with the permissions inherited from the spoofed device, maybe even spread further if the media server isn’t set up securely.

    In my mind I could prevent this with authentication, as I could force a device to have a keyfile or something in order to use that IP address. So the bad actor would at least first need to get access to the real device and steal the keyfile in order to spoof it. Which (in my mind) is way harder than iterating through all Mac addresses and testing which addresses get which IPs with which permissions.

    The issue i want to solve (with this part) would basically boil down to: securely giving different permissions to devices on the same network/subnet.

    The only other way I would see would be to buy more APs so there is a separate WiFi for every set of permissions I want to give out, so spoofing Mac addresses becomes irrelevant.


  • I’ll try to do a diagram tomorrow. Its a mixed network of multiple families of whom some want to host a server to the internet. That would mean lots of untrusted traffic, so I get more concerned with auth. If I know the Mac address and IP I want to spoof, I can get the permissions of the device I spoofed, as long as I am in the same subnet, which is the case for wifi (ap can only host 4 different ones, I have more than 4 groups of user permissions so I can’t separate them all). That’s where some auth would come in in my mind.

    The problem is, I just learned about how to use the software, I am far from deep enough in it (and IT-knowledge in general) to actually pen test myself, I would have no idea how someone would worm through my network, if he gets rce on the server of one of the other families, so I can’t really say if something like this is possible or not.



  • Thanks for you thoughts! It will take a while to go through the tools, but having a list really helps.

    For the auth, you are suggesting that clients on the same subnet should always have the same permissions?

    Usecase would be: We have a WiFi for family A, mother shall get access to the media server on a different subnet, tech savy son should not get acces to it. We have client isolation, but that would not stop the son from “stealing” the IP address his mom uses by spoofing their Mac address. I dont see how client isolation would help here, but I would need some kind of auth approach.

    Sure putting them on different subnets would be an elegant solution, but I can only host 4 wifis from my ap and have more than 4 “permission groups”



  • Well I have separate subnets for separate vlans. Connections between them get blocked by the firewall by default from my understanding, but to be safe I explicitly deny all outbound AND inbound connections, so I have to make a rule for each of two subnets if I want inter subnet communication, which is the case for the shared media server. If I do that I whitelist which IPs can reach which IPs on the different subnet. There still is the problem that different clients on the same network can "steal"the IP of other clients with more permissions. That’s why I asked about authentication


  • I tried that a little, but my problem was that there was to much stuff going on in the network for me to understand and review all. I am currently not reachable at all from the big internet, only local server access and I only get working connections if I rset an IP corresponding to the vlan I am in, but unify broadcasting, Nat, VPN, etc. Make a lot of connections and connection attempts internally I dont understand.

    Problem with no client authentication is that the network is used by multiple separate households not necessary trusting each other, and some now want to host servers to the public, which would mean lots of untrusted traffic. I am concerned if they dont handle their security right and have access to for example our shared media server, they could scrape ip-mac address pairs to get deeper in the network. Any thoughts on benefits and lows of 802.1 vs. Radius?


  • Okay, yeah i do look at the reporting to Register things that look off, but I am not sure I recognize everything that IS off.

    Generally I keep outbound and inbound completely closed except for the connections I need, which I manually allow for in the rules for each subnet. for the client WiFi I have a alias with all private (ipv4) ranges, and a rule that allows outbound to anything but that (so only connections to “the internet” not to stuff in my network.

    Radius is the thing I at least came across a few times in my settings, from what I understand I would need a dedicated radius server all can reach an authenticate against right? At the moment I only have a bare metal Debian server for the self hosted unifi controller, maybe I could learn proxmox and do radius and unifi in different VMs on that machine.

    What would the tailscale option mean? I have heard about it (but mostly mentioned in combination with arr stacks, which I dont have, so I never looked at it. What does it do? What are the benefits over for example radius?

    Okay, so radius/tailscale for client networks, for iot I rely on subnet separation would be your advice?






  • Well, i never argued against the clearly powerfull capabilities, those are obviously huge, my point was that as a hobbyist you should consider having the important stuff (finances, official documents, biometrics) in cold storage or on a separate machine as well as stuff like security cameras or doorlocks if you do stuff like this out of it until you fully understand the risks, which are not that easy to grasp for people without experience.

    Ofc proxmox and qubes are incredible useful tools of technology, but their high versatility and customizability gives you a lot of tools you need understand and use properly on top of what you are already doing. (More so with proxmox as with qubes, qubes is a little less industry focused IMHO)




  • Thanks for evaluating! The exploit was explained to me that an unpriviliged user/Programm could use it to get root access on the whole system, which I my mind included the hypervisor. Further reading seems to proof you right, while containers were broken VMs were not.

    My point still remains, although weaker: If you know exactly what you are doing you can get a system quite secure, if you are a hobby server owner like me, its not that easy. I would have not know that the use of VMs instead of containers has sooo major security implications, that something so fundamental as ssh could be exploited in such large scales, and clustering would have been needed to avoid being unsafe.

    Sure, noone would use an zero day on me targeted, the thing is: I am not working in the field, from publishing of the exploit till learned about it and had the time to patch, there were a few weeks. If in those few weeks someone deploys a tool going for mass and not for single targets, I would probably be infected and added to some botnet, cryptominer or whatever.

    If I have a bare metal dedicated server, which has only access to IPs contained in my whitelist on a dedicated opnsense, I have less to wory about. Sure, someone could still find a openbsd/opnsense exploit and get me, but my point is: complex systems break in complex ways, the more complex systems you use, the more attack surface u have, need to know and understand to control and mitigate it.

    Not that its impossible, but for a hobbyist who tries to self teach with man pages, tutorials and forums, you can get pwnd in unexpected ways (like because you used a container for dodgy Chinese smart home devices and expected that your production environment would be safe even if one of them was malicious, but in fact you were not, because that would have needed to be a VM. AND: before copy fail was published, users would have probably also told you that containers are safe.