Disclosure: I'm CTO at Fleet. One of the biggest challenges is the vendor lock-in that results from the way the MDM systems work (particularly on macOS). In typical MDM solutions you don't own the keys and can't manage migrations without direct interaction from every end user. We expect Broadcom to milk this friction while they can.
One of my fav things about this is that we're solving the "Linux MDM problem". As a person who likes to use Linux, it's exciting that, no matter how big the company gets, I can still use whatever OS I want at work (and still be "offboard-able", with everyone passing their audits.)
One of my favorite things about this is that we are bringing a GitOps workflow to IT teams. As a software engineer myself, seeing change management and CI coming to other domains within the organization is incredibly exciting!
Ansible is primarily a "push" model, which is hard with systems which may or may not be online from various locations (eg laptops).
Plus having a cross platform MDM would allow an IT team to manage a fleet of end user devices without having to become experts in each of them. For example, the MDM could have push button "erase this machine", etc
Very good point on the push model when it comes to devices like laptops.
Not sure how I feel on the second point. Managing Linux at scale, aside from the laptop point is pretty easy. Maybe companies need better help desk employees.
This is an interesting looking product. I grew lettuces using the Kratky method in cheap plastic bins and some standard shelving units, which was relatively low effort and had tremendous results at about 25% the cost of this unit (but much less stylish). This looks like a decent intro guide on Kratky: https://www.trees.com/gardening-and-landscaping/the-gratky-m...
There was a similar instance of a fake student living on Stanford campus about 20 years ago. I wonder if this is common among elite schools, or if Stanford has some special draw?
Fun! I kept thinking about doing this. Love your idea to use the dot-matrix tool. Maybe next a GitHub action to keep it updated and/or change it over time?
Fleet is building an open future for device management. Open APIs you can use from anywhere. Transparency for end-users. Trust built on an open-core foundation.
We are looking for an Engineering Manager on our Agent team. This position will be responsible for managing the engineers and strategy for:
- Osquery across Windows, macOS, and Linux.
- Fleet's agent update system based on The Update Framework.
- Fleet Desktop (Desktop application for user notifications and self-remediation).
- MDM features.
Join our team of friendly and competent engineers to expand our 100% source-available (github.com/fleetdm/fleet) endpoint management product. We work closely with the osquery community, and have both paying customers and open-source users from organizations you’ve heard of. We’re backed by CRV and Sid Sijbrandij (CEO of GitLab).
This role will report directly to me (CTO), please reach out with any questions: zach[at]fleetdm.com
In theory osquery is "just" virtual tables, but in practice there's quite a bit more that would probably make attaching it to mvsqlite. If you have a use case in mind I would love to know!
I would be commending them if this notice went out March 3 after they had remediated the problem and were aware that they had no logs to determine whether there was abuse.
