Yes, I am aware.
I'm more asking if others are getting a wide spread of threatening messages across the org - even if they don't regularly use conda/anaconda.
It's like everyone glossed over "I don't use it in my job at all, and neither do my teammates" bit.
Send the emails to your company’s legal team. It’s not your fight.
Already did, and agreed. I also asked the legal team if they could ask Anaconda.com to stop contacting me and threatening me personally. We shall see what happens.
I'm not here to discuss the nuances of a startup versus medium sized company. Suffice it to say that much of the organization still views itself as a startup. Even though yes, you are right, it's a medium sized organization.
Sure. I can agree that my company would be liable. But the company isn't mine. I just work here. And my team doesn't use any conda stuff at all.
Essentially, I am being personally threatened of a lawsuit even though I have no ability to make a licensing or purchase decision.
That just doesn't sit right with me.
TPMs can be extracted with physical access
Sure, but IIRC, they'd still need my PIN (for TPM+PIN through cryptenroll). I don't think it's possible to do TPM backed encryption without a PIN on Linux.
EDIT: Oh wait, you can... Why anyone would is beyond me though.
This sounds like a lenovo machine. Or something with a similar MOK enrollment process.
I forget the exact process, but I recall needing to reset the secureboot keys in "install mode" or something, then it would allow me to perform the MOK enrollment. If secureboot is greyed out in the BIOS it is never linux's fault. That's a manufacturer issue.
Apparently, some models of Lenovo don't even enable MOK enrolment and lock it down entirely. Meaning that you'd need to sign with Microsofts keys, not your own. The only way to do this is to be a high-up microsoft employee OR use a pre-provided SHIM from the distribution.
For that case, Ubuntu and Fedora are better because, per the Ubuntu documentation they do this by default.
On Ubuntu, all pre-built binaries intended to be loaded as part of the boot process, with the exception of the initrd image, are signed by Canonical's UEFI certificate, which itself is implicitly trusted by being embedded in the shim loader, itself signed by Microsoft.
Once you have secureboot working on Ubuntu or Fedora, you could likely follow these steps to enable TPM+PIN - https://wiki.archlinux.org/title/Systemd-cryptenroll#Trusted_Platform_Module
There might be some differences as far as kernel module loading and ensuring you're using the right tooling for your distro, but most importantly, the bones of the process are the same.
OH! And if you aren't getting the secureboot option in the installer UI, that could be due to booting the install media in "legacy" or "MBR" mode. Gotta ensure it's in UEFI mode.
EDIT: One more important bit, you'll need to be using the latest nvidia drivers with the nvidia-open modules. Otherwise you'll need to additionally sign your driver blobs and taint your kernel. Nvidia-Open is finally "default" as of the latest driver, but this might differ on a per-distro basis.
Yeah, no kidding. The same systemd that enables the very things OP is trying to enable...
systemdboot + sbctl + systemd-cryptenroll and voila. TPM backed disk encryption with a PIN or FIDO2 token.
AFAIK this should be doable in Ubuntu, it just requires some command-line-fu.
Last I heard the Fedora installer was aiming to better support this type of thing - not so sure about Ubuntu.
Hahah, good luck. Proton Drive is really terrible. I can't even upload a single 1GB file through the service.
Well, I mean, most corps trying to shoehorn AI into things are using Cloud implementations of the various "AI" solutions.
What, pay for our own datacenter? Nah.
Just import openai and add "the AI" that way. 🤦♂️
Fair, and I think I'd have gone that direction if it wasn't a slack channel where everyone was invited to, and then questioned if they decided to leave. It was also a very noisy channel where it was disrupting my work.
I didn't just throw this into some channel in which I wasn't invited or anything. I actually felt like I wasn't allowed to leave, which is why other NDs privately thanked me afterwards.
I can ignore the ignorable, but if you're going to hunt me down if I ignore it (like they were doing), then I needed to speak up in order for it to stop.
Typically I do just what you've described, just kinda ignore it.
The real kicker is that I'm fairly sure we aren't really using them at any real scale - if we do it's to demo our product within the context of AI development. So if anything, they get a lot of free press when we do that. If they're gonna throw a fit over it, I'm sure we can work with some other "AI" company (that's what they bill themselves as) that wants the free marketing. Heck, I can't imagine the anaconda ecosystem working out if they keep threatening the developers that enrich that ecosystem.