The Stoned Hacker

Just passin’ through

  • 1 Post
  • 17 Comments
Joined 3 years ago
cake
Cake day: June 24th, 2023

help-circle

  • You’re wrong, containerization is a massive security measure that shouldn’t be ignored. Proper containerization allows you to segment the namespacing of a single server by user and application; this helps massive with esrablishing boundaries that are still very difficult to cross under normal circumstances. Keycloak is an IdP which only provides one layer of security; good swcurity implements defense in depth where every layer of the system has securiry measures. Just because Linux recently had two vulnerabilities that bypass a lot of those doesn’t mean they’re worthless; you still need initial access to a nonprivileged user to exploit those and layered security can help prevent that from happening in the first place.










  • I do this for my containers. I have a completely domain-managed network, so my docker/podman host mounts an NFS share that contains all the data volumes for my services. Each one only has read permissions for the service account that runs it (and has nogroup). Each OCI container mounts their data volume(s) from their respective directory as well as a kerberos user TGT and credentials cache. Each OCI container runs as the service account, which uses the kerberized credentials to access the mounted data volumes (this is necessary), and thus I acheive separation. Even if a threat actor were to compromiee a service they would still be locked down to that service account and only able to access/modify the data of this service. This is still be very bad for services like keycloak, but for other trivial services it almost guarantees more than adequate segregation. This does fall apart a little bit with the recent copyfail and dirtyfrag exploits which allow for easy privilege escalation, but I don’t allow root squash so the data volumes on the NFS share are still service_account:nogroup even when accessing as root. Now an attacler could go through and use the KRBTGTs that are stored for each service account to access the data, but at that point I am dealing with a dedicated threat actor. Defending against someone explicitly seeking to compromise me is a different situation altogether, and still requires initial access through a vulnerable application that is sitting behind an SSL termination proxy and an NGFW with IPS capabilities.


  • It seems they literally meant what commands are your favorite. Bash is a shell but it is just as much a command (bash -c 'wall poop'), and ssh and man are some of the most widely used commands on linux (if you end up working with LXC containers many of them do not come with manpages preinstalled. I highly recommend installing them if you’re going to spend any of amount of time on thr LXC)





  • i think the best example of this is music. most people have very good relative pitch perception, but mediocre absolute pitch perception. that shared relative pitch perception though will often be built based on ones own experiences and life. the shared perceptual relativity is both developed socially/culturally and innate based on how we process and abstract information, but that says nothing about our absolute perception of that information.