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

help-circle

  • LXC is namespaces only, maybe you’re thinking of libvirt I stand corrected about LXD, never knew it did that, weird I don’t know why you’d wanna do that instead of using libvirt.

    Flatpack uses namespaces. And unless you have it disabled in the kernel, namespaces can be nested. There’s nothing stopping a browser running a flatpack from using namespaces itself.

    Not to say that you are incorrect about namespaces vs security. Namespaces are not as secure as a VM.



  • Second is that it runs on AWS. This isn’t a problem in the sense that it’s possible for it to still retain privacy while running on AWS. Some people don’t like it because they view the dependence on the infrastructure of an American company to be a risk to availability. They also believe that it would exacerbate a security flaw if one were found.

    Let’s not pretend the hypervisor doesn’t have full access to the VMs memory and execution. The only thing protecting the Signal server is Intel SGX.












  • Absolutely. Simply use ACME with the DNS validation method. Using bind you’ll want to create keys and allow TXT access for those keys to the validation domains. Fear not, this isn’t exclusive to bind, ACME tools supports dozens of other backends. That’s all you need the actual domain doesn’t need to be resolvable with an A/CNAME record. Internally you can run an entirely different DNS server to resolve your hosts, use hosts files, or use bind zones.


  • Except it isn’t. Saying it is trivial is just gross generalization. It’s trivial to configure bind to have internal zones that aren’t resolvable publically. It all depends on configuration, such as reverse ns entries, zone accessibility, etc.

    You can have (sub)domains that are listed in the certificate lists and yet aren’t resolvable externally as well.