Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)F
Posts
22
Comments
868
Joined
3 yr. ago

  • Hmm. What about CAD? The professor going to teach FreeCAD, OpenSCAD, F360, OnShape, etc?

    I think requiring one tool is OK. You're there to learn the process in a way that you can migrate to what you want later. Teachers aren't paid enough as it is, so it should be made as easy as possible for them to manage the flow of work.

  • Drag them across the corner of the counter, pulling down as you do. Works great.

  • All brains should aspire to work like your brain.

  • ZFS. Since it backs up at block level, moving giant files means you onoy send a few K for the backup, unlike other solutions like rsync, etc.

  • I hate any company that uses or builds AI to screen out hires so, so much. Tagging metadata is OK, but filtering is just evil (am/have been a hiring manager).

    The company also added that it’s instituting a bug bounty program to better catch security vulnerabilities in the future. “We do not take this matter lightly, even though it was resolved swiftly and effectively,”

    I also hate it more that I can't hate them for doing the right thing.

  • Instead of having to do service.domain.tld it's nice to do service.lan.

  • I wrote scripts to automate my own custom ZFS multi-site backup solution. Way harder than spinning up a purose-built NAS OS, but not only do I have full control over it, I learned so much more about the underlying filesystem than I ever would have.

  • I use a dual NIC mini PC running OpnSense. Ot would support USB sims. I actually have two of the routers connected woth a network cable. If one goes down, the other takes over.

  • I'm not sure I follow the question. All of the TLD *.arpa is not reserved for private use, only *.home.arpa. So all your internal services are required to be a sub domain.

  • Sometimes it's to artificially narrow the lane to slow traffic. That's what they did here.

  • But.. your original comment is just.. wrong?

    This isn't a critical security flaw unless you have the worst partition scheme on your encrypted volumes imaginable.

    The default LUKS partition scheme is vulnerable.

    It's not even a process flaw at that point, just "possible".

    There is a successful POC, it is a flaw.

    you can compromise disks once encrypted because everything is happening in an in-memory boot process.

    This is not just in-memory. This is modifying the unencrypted part of initramfs on disk. Powering off the machine does not remove the exploit.

  • You always "boot something that is unencrypted." You then "mount" the encrypted volumes and load the OS.

    This is how people can put an SSH server (dropbear) in initramfs so they can unlock remotely.

    The attack is to initramfs, not the encrypted layer.

    The order'ish:

    • Boot
    • Initramfs loads, gives you the LUKS prompt
    • Initramfs decrypts/mounts OS
    • OS loads
  • I'm confused.

    Initramfs is unencrypted in /boot when using LUKS with RAID. It has to be, right?

    The attacker uses a debug shell to modify the unencrypted boot, so the next time you boot and type your LUKS password, they can gain access.

    This doesn't line up with your comment?

  • A fun conversation starter is always "So do you have an internal monologue?"

  • No thanks. I get some people agreed to this, but I'm going to continue to use .lan, like so many others. If they ever register .lan for public use, there will be a lot of people pissed off.

    IMO, the only reason not to assign a top-level domain in the RFC is so that some company can make money on it. The authors were from Cisco and Nominum, a DNS company purchased by Akamai, but that doesnt appear to be the reason why. .home and .homenet were proposed, but this is from the mailing list:

    1. we cannot be sure that using .home is consistent with the existing (ab)use
    2. ICANN is in receipt of about a dozen applications for ".home", and some of those applicants no doubt have deeper pockets than the IETF does should they decide to litigate

    https://mailarchive.ietf.org/arch/msg/homenet/PWl6CANKKAeeMs1kgBP5YPtiCWg/

    So, corporate fear.

  • I just use openssl"s built in management. I have scripts that set it up and generate a .lan domain, and instructions for adding it to clients. I could make a repo and writeup if you would like?

    As the other commenter pointed out, .lan is not officially sanctioned for local use, but it is not used publicly and is a common choice. However you could use whatever you want.

  • I use a domain, but for homelab I eventually switched to my own internal CA.

    Instead of having to do service.domain.tld it's nice to do service.lan.