The proliferation of new top-level domains (TLDs) has exacerbated a well-known security weakness: Many organizations set up their internal Microsoft authentication systems years ago using domain names in TLDs that didn’t exist at the time. Meaning, they are continuously sending their Windows usernames and passwords to domain names they do not control and which are freely available for anyone to register. Here’s a look at one security researcher’s efforts to map and shrink the size of this insidious problem.

  • magic_smoke@links.hackliberty.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    4 months ago

    Pretty much. Its nice but I find trying to get it to do anything other than cookie cutter operations requires you to not only go around the GUI, but in many cases break it.

    Also lotta shit that was supposed to work sucked too. The GUI always seemed to have a 50% chance of clobbering my ACLs when editing them, and encryption was either entirely password based, or the keys where stored with no passphrase on an unencrypted dataset.

    My rocky nas has Luks on mdraid for the root which hold the keys for the zfs pools, and CLI based acl management is pretty ezpz once you learn it.