platform-compat VS distrobuilder

DotNet offers the SecureString class to keep a string encrypted in Memory, but as long as the OS does not natively support this concept, the only advantage is that it resides in memory for a shorter time, the disadvantage is that SecureStrings are easier to search for.

Note the KeePass's resistance to the attack mentioned depends on the security of .NET's secure string, which, here's what Microsoft has to say about it (https://github.com/dotnet/platform-compat/blob/master/docs/D...)

As for KeePassXC, last I checked it didn't even bother.

TIL. Looks like the deprecation note recommends MailKit.

Well of course, but it does have to be passed to the module that generates the hashes AD uses in the first place. And as I said, the standard password reset screen is bound to store the password in plain text somewhere as well.

This won’t help you with your question, but I figured I should warn against using send-mailmessage.

points you here.

Some of the reasons for not using Hashtable or other non-generic collection types are outlined here. That's why Microsoft doesn't recommend their usage in new implementations across all of its API documentation.

And if you really want to be secure you need to something better than a SecureString: https://github.com/dotnet/platform-compat/blob/master/docs/DE0001.md

Working with legacy applications that needed full system access taught me that a different way to do containerization is by using LXC/LXD. The focus in system containers, rather than application containers, can be thought of like a light VM rather than what most consider the typical container.

LXC provides system-level containerization, offering a different approach focused on creating environments that more closely resemble traditional virtual machines.

Linux Container Daemon (LXD) is a container and virtual machine manager developed by Canonical. It provides flexibility by offering a single process for multiple containers. It connects to the Linux container library (LXC) using a REST API. It is an add-on to LXC, providing more features and functionalities.

Docker introduced their new container technology at PyCon 2013. At this time, Docker containers were just a wrapper for Linux Containers but this fundamentally changed the landscape of computing (more on this later).

LXC

which is what docker/podman/containerd use. If you want full system emulation look into LXC/LXD.

LXD is a manager for Linux Containers (LXC), which lets me spin up a kind-of lightweight VM for any distro, instantly. I use it to run proprietary software isolated from the rest of my system (such as Steam); disposable environments for trying stuff out, and running software that doesn't jive well with Nixos.

Check this thread on linuxcontainers LXD forum. Half way down Simos points to the eventual solution: