I run Slackware on most of my systems.
Servers run Slackware, hosting Linux Containers running Slackware. Containers run my domain, web hosts, file server, and game servers.
Desktops run Slackware.
Laptop is a MacBook Air, so runs macOS.
I run Slackware on most of my systems.
Servers run Slackware, hosting Linux Containers running Slackware. Containers run my domain, web hosts, file server, and game servers.
Desktops run Slackware.
Laptop is a MacBook Air, so runs macOS.
Yeah, in 2025 doing encrypted email is a painful process. Every option is a hack on top of a 43 year old protocol.
Here is a howto from Mozilla on pgp with Thunderbird. It isn’t a pleasant process.
https://support.mozilla.org/en-US/kb/openpgp-thunderbird-howto-and-faq
Communication between the email servers is normally encrypted with TLS. The email files themselves are rarely encrypted. Most providers that do encryption of email are using local server managed encryption, so the email providers would still be able to access it.
For proper end to end protection you would want to setup PGP between you and your recipients, and encrypt the email before its sent.
Samba 4 implements Active Directory, last time I looked it was up to 2012 functional level. Samba provides a cli tool, samba-tool for managing Samba. So you don’t have to use other tools for managing it, but it is often much easier using Microsoft’s RSAT than the cli tool.
Microsoft Terminal supports tabs and custom profiles. It can host Azure CLI, PowerShell, CMD.exe, and Bash.
Windows ships with openssh that is usable in any of the supported cli.
I use it all the time for work to ssh into systems.