John Richard

Well, first they are lying to you. You don’t have to hand out certificates manually and that isn’t how Intune does it either. They are provisioned using SCEP generally, which has its own security drawbacks. You can get these certificates from a SCEP server using a tool like Certmonger.

Most companies that say they don’t officially support Linux already have you sign an acceptable-use agreement to only use company-provided hardware and approved software. And while they may act like they’ll make a special exception for you, you better make sure you got it in writing and in a way that would comply with your other employment agreements. One thing most IT employees don’t have the privilege of is negotiating the legal terms of their employment. There are already multiple US cases of employees being criminalized for breaking their employer’s AUP.

I wish you the best of luck, but feel like you’re prob in for a harsh reality.

You can use Wi-Fi certificates on Linux without needing Intune. Is the real issue here that your workplace doesn’t want to give you the info you need to use Linux?

What would having Intune offer you personally? Are you a smart Linux user or barely know enough to be dangerous?

Go to your IT department or management and tell them you want to use Linux for work if that is what you want, and if they say no then make up your mind if you’re willing to become a braindead zombie for the company, or if you’d rather be doing something actually useful and meaningful with your time.

Such a security risk though, but still better than curling scripts into sudo

Now Drew Devault can finally work on PizzaHut.

Sysv didn’t have to have a lot of documentation. It was simple to understand what it did, and the underlying system was mostly shell scripting. It didn’t try to be and do everything.

I don’t hate systemd. I prefer it now for the most part. I really do think Lennart Poettering is incredibly skilled and intelligent. I am just frustrated that so much gets pushed without adequate resources and support to weigh what is production-ready, and what is bleeding edge. I’ve already had systemd bite me in the ass at least once where they made a significant unannounced change to systemd-cryptsetup. I had to go find answers by reading through pull request and GitHub issue comments, and it wasn’t easy to find either. The community acted like it wasn’t a big deal that it caused systems to no longer boot. Move fast & break things isn’t the message that will win over larger companies.

Lennart Poettering is no doubt smart, but learning all the ins and outs of systemd with terrible documentation and half-baked solutions, and just “trusting” it to do everything from UEFI booting, immutable partitions, system imaging, networking, home directory and resource management, init and daemon processes, sockets, etc. using “INI-like” files… hmm, I’d almost prefer another global outage.

It means that questioning decisions or problems is seen as negative in the community generally and that everyone else must be wrong for not using NixOS.

As I used to say. The Nix community acts more like a cult of people willing to support flat earth.

deleted by creator