Just as advice, please don't declare namespaces using the "using namespace <namespace_name>". Unless you know what functions are implemented inside of it, if two namespaces have the same function name in both of them with different implementations, the compiler will run the function based on the namespace you have declared using the "using namespace <namespace_name>."

It is better, for example, instead of instatiating the namespace "using namespace std" you should do std::cout << "your_string" << std::endl this is explicitly saying from the std namespace, get cout, and from std namespace, get endl. It is more clear it is concise and everyone knows where you are getting this function from. Whereas if you did "using namespace std" and then cout << "your_string" << endl no one knows where you are getting those functions.

Explicitly instantiate your namespaces at the time you declare your functions inside said namespaces even if it means tediously writing out the namespace every instantiation, it makes reading your c++ code that much more easier.

  • source
  • [–] 3 points 1 week ago

    It's just a 'proper' IPv6 private address, the IPv6 equivalent of '10.'.

    I say proper as a private address in ipv6 is supposed to be fd, then 40 random bits, then whatever you want. Nothing stops you from having fd::/64 as your private network though. The thinking was people who got tired of merging networks that happened to choose the same 10.x.x.x scheme and/or vpn connecting to multiple sites similarly with the same private address. So they thought it would be swell if every private network on earth would likely be unique, so they said you 'must' randomize 5 bytes of it. Then no renumbering/no conflicting vpn connections.

  • source
  • parent
  • context
  • [–] 1 point 1 week ago

    Further the audit log that you pretty much always need to consult when something fails for mysterious reasons in case it might be SELinux isn't even readable by the user that got dinged. So I can't even code in a way to check if SELinux was the reason and guide the user, instead I have to provide a diagnostic utility they have to 'sudo' to explain to them, or be vague and say 'check if selinux is somehow involved. So I end up despite doing my damndest to not run with privilege asking users to run something with privilege to check a security mechanism.

    fedora preinstalls a tool that warns users if they have tripped up in selinux, and provides dome details

    alerts are shown to the user in desktop notifications, and there's a gui tool with some actions

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