[–] 4 points 1 week ago (4 children)

Well technically a 10. network could be a /8 if you really wanted to. But in this case the /23 was specified above. I don't think it's necessary but that's what op was talking about and the 212.255 is a valid address, as is 213.0

  • source
  • parent
  • context
  • [–] 125 points 1 week ago (8 children)

    10.0.0.0/8 address space with a gateway address that gets randomized every 24 hours. Tomorrow's address is advertised on a HTTP server local to the network that cannot be externally accessed. For security reasons.

  • source
  • [–] 10 points 1 week ago* (5 children)

    My soho setup is:

    1-100 = DHCP

    101 = Default gateway

    102 - 199 = Unused

    201-254 = Static, manually assigned IPs (if any)

    I came up with it before I got my Net+. I told myself I'd change it as soon as it caused any problems. That was 12 years ago.

  • source
  • parent
  • context
  • [–] 5 points 1 week ago

    Even projects that expressly prohibit AI code still have AI code in them. It's damn near impossible to actually enforce. I don't like AI code but I know I can't avoid it so I don't see the point in trying.

  • source
  • [–] 1 point 1 week ago

    In some usecases SELinux is less flexible:

    You have two applications installed which bring their own labels and rules, lets say app_a_t and app_b_t. Now you want to give AppA read access to only one specific directory of AppB data (which is labeled app_b_t).

    How to do that? Writing a rule allowing acces between the labels would give AppA access to all of AppB data. Creating a new label for this specific dir would break AppB as it relies on the rules for app_b_t.

    My biggest issue with SELinux is that files and applications can not have multiple types at once (like with a role based model).

  • source
  • parent
  • context
  • view more: β€Ή prev next β€Ί