Top
Best
New

Posted by hornedhob 1/27/2026

Lennart Poettering, Christian Brauner founded a new company(amutable.com)
375 points | 736 commentspage 5
Phelinofist 1/28/2026|
Why have the responses to the post from the CEO been moved to their own top-level posts? Also, why are replies disabled for the CEO post?
egorfine 1/28/2026|
Because the feedback is overwhelmingly negative and thus deemed useless for them.
devsda 1/27/2026||
The immediate concern seeing this is will the maintainer of systemd use their position to push this on everyone through it like every other extended feature of systemd?

Whatever it is, I hope it doesn't go the usual path of a minimal support, optional support and then being virtually mandatory by means of tight coupling with other subsystems.

DaanDeMeyer 1/27/2026||
Daan here, founding engineer and systemd maintainer.

So we try to make every new feature that might be disruptive optional in systemd and opt-in. Of course we don't always succeed and there will always be differences in opinion.

Also, we're a team of people that started in open source and have done open source for most of our careers. We definitely don't intend to change that at all. Keeping systemd a healthy project will certainly always stay important for me.

bayindirh 1/27/2026|||
Hi Daan,

Thanks for the answer. Let me ask you something close with a more blunt angle:

Considering most of the tech is already present and shipping in the current systemd, what prevents our systems to become a immutable monolith like macOS or current Android with the flick of a switch?

Or a more grave scenario: What prevents Microsoft from mandating removal of enrollment permissions for user keychains and Secure Boot toggle, hence every Linux distribution has to go through Microsoft's blessing to be bootable?

DaanDeMeyer 1/27/2026|||
So adding all of this technology will certainly make it more easy to be used for either good or bad. And it will certainly become possible to build an OS that will be less hackable than your run of the mill Linux distro.

But we will never enforce using any of these features in systemd itself. It will always be up to the distro to enable and configure the system to become an immutable monolith. And I certainly don't think distributions like Fedora or Debian will ever go in that direction.

We don't really have any control over what Microsoft decides to do with Secure Boot. If they decide at one point to make Secure Boot reject any Linux distribution and hardware vendors prevent enrolling user owned keys, we're in just as much trouble as everyone else running Linux will be.

I doubt that will actually happen in practice though.

cwillu 1/27/2026|||
I would be _shocked_ if, conditional on your project being successful, this _wasn't_ commonly used to lock down computing abilities commonly taken for granted today. And I think you know this.
jacquesm 1/27/2026||||
> So adding all of this technology will certainly make it more easy to be used for either good or bad.

Then maybe you shouldn't be doing it?

egorfine 1/28/2026||||
> we will never enforce using any of these features in systemd itself. It will always be up to the distro

So, plausible deniability. It's not the systemd project, it's the distro.

> I certainly don't think distributions like Fedora or Debian will ever go in that direction.

In the past they made decisions that we can call unexpected. I believe that in the short term future they won't but in say ten years? I'm not sure. The technology (created by Amutable?) will be mature by that time and ready to close Linux down.

alextingle 1/28/2026|||
Building stuff like this is wrong. You should find a different job.
ongy 1/27/2026||||
Hopefully cartel regulation would prevent Microsoft from using their market leader position to force partners to remove all support for competitors.

But I'm losing hope with those.

Cu3PO42 1/28/2026||||
> What prevents Microsoft from mandating removal of enrollment permissions for user keychains and Secure Boot toggle

Theoretically, nothing. But it's worth pointing out that so far they have actually done the opposite. They currently mandate that hardware vendors must allow you to enroll your own keys. There was a somewhat questionable move recently where they introduced a 'more secure by default' branding in which the 3rd party CA (used e.g. go sign shim for Linux) is disabled by default, but again, they mandated there must be an easy toggle to enable it. I don't begrudge them to much for it, because there have been multiple instances of SB bypass via 3rd party signed binaries.

All of this is to say: this is not a scenario I'm worried about today. Of course this may change down the line.

egorfine 1/28/2026||
> today. Of course this may change down the line.

Given Microsoft's track record I don't believe this will stay that way for long.

trelane 1/28/2026||||
> What prevents Microsoft from mandating removal of enrollment permissions for user keychains and Secure Boot toggle, hence every Linux distribution has to go through Microsoft's blessing to be bootable?

Why are you buying hardware that Microsoft controls if you're concerned about this?

egorfine 1/28/2026||
With TPM, Microsoft controls practically all the Intel hardware.
noosphr 1/27/2026|||
Nothing, but openbsd is amazing and just works. Anyone still using Linux on the desktop in 2026 should switch.
bayindirh 1/27/2026|||
"Just don't use X" doesn't solve any problems in any space, unfortunately.

Plus, it's an avoidant and reductionist take.

Note: I have nothing against BSDs, but again, this is not the answer.

noosphr 1/27/2026|||
It works for me and for millions of others.

Stop trying to make everyone act like you act.

justinsaccount 1/27/2026|||
> Stop trying to make everyone act like you act.

Yeah! Telling people what to do is rude!

> Anyone still using Linux on the desktop in 2026 should switch

Oh.

bayindirh 1/27/2026|||
I'm not trying to make everyone act like I act.

Also, I know. A few of my colleagues run {open, free, dragonfly}BSD as their daily drivers for more than two decades. Also, we have BSD based systems at a couple of places.

However, as a user of almost all mainstream OSes (at the same time, for different reasons), and planning to include OpenBSD to that roster (taking care of a fleet takes time), I'd love to everyone select the correct tool for their applications and don't throw stones at people who doesn't act like them.

Please remember that we all sit in houses made of glass before throwing things to others.

Oh, also please don't make assumptions about people you don't know.

waynesonfire 1/27/2026|||
You could describe Richard Stallman as someone who refuses to use proprietary software because he sees using it as becoming complicit--however indirectly--in a technology ecosystem that violates the values he’s committed to.

"Just don't use X" is in fact a very engaged and principled response. Try again.

yjftsjthsd-h 1/27/2026||||
(I like OpenBSD, but) It is extremely hard to compete with Linux on hardware support / driver coverage.
johnny22 1/27/2026|||
I like the GPL for the kernel, so I wouldn't switch.
direwolf20 1/27/2026||
What should I do if I like AGPLv3 kernels?
johnny22 1/28/2026||
then you'd have a write a new kernel
devsda 1/27/2026||||
Thanks Daan for your contributions to systemd.

If you were not a systemd maintainer and have started this project/company independently targeting systemd, you would have to go through the same process as everyone and I would have expected the systemd maintainers to, look at it objectively and review with healthy skepticism before accepting it. But we cannot rely on that basic checks and balances anymore and that's the most worrying part.

> that might be disruptive optional in systemd

> we don't always succeed and there will always be differences in opinion.

You (including other maintainers) are still the final arbitrator of what's disruptive. The differences of opinion in the past have mostly been settled as "deal with it" and that's the basis of current skepticism.

DaanDeMeyer 1/27/2026||
Systemd upstream has reviewers and maintainers from a bunch of different companies, and some independent: Red Hat, Meta, Microsoft, etc. This isn't changing, we'll continue to work through consensus of maintainers regardless of which company we work at.
egorfine 1/28/2026||
> companies

That's the keyword.

Companies. Not people.

s_dev 1/27/2026||||
>We are building cryptographically verifiable integrity into Linux systems. Every system starts in a verified state and stays trusted over time.

What problem does this solve for Linux or people who use Linux? Why is this different from me simply enabling encryption on the drive?

NekkoDroid 1/27/2026|||
Drive encryption is only really securing your data at rest, not while the system is running. Ideally image based systems also use the kernels runtime integrity checking (e.g. dm-verity) to ensure that things are as they are expected to be.
cwillu 1/27/2026||
“ensure that things are as they are expected to be” according to who, and for who's benefit? Certainly not the person sitting in front of the computer.
NekkoDroid 1/27/2026|||
The system owner. Usually that is the same entity that owns the secure boot keys, which can be the person that bought a device or another person if the buyer decides to delegate that responsibility (whether knowingly or unknowingly).

In my case I am talking about myself. I prefer to actually know what is running on my systems and ensure that they are as I expect them to be and not that they may have been modified unbeknownst to me.

direwolf20 1/27/2026||
I don't think this is right. Usually, the entity that owns secure boot keys is a large tech corporation which paid to install their keys on all new computers.
marcthe12 1/28/2026||
You can enroll your own and LP goal is basically based on the assumption that you can enroll your own
egorfine 1/28/2026||
Until you cannot.
rcxdude 1/27/2026|||
This is only the case if the person sitting in front of it does not own the keys.
cwillu 1/27/2026||
And from this you can safely conclude that users will be under severe pressure to surrender them.
Nextgrid 1/27/2026|||
It prevents malware that obtained root access once from forever replacing your kernel/initrd and achieving persistence that way.
direwolf20 1/27/2026||
Unless that malware is able to activate the secure boot feature on a system where it is not enabled, in which case it permanently prevents me from removing the malware.
Nextgrid 1/28/2026||
Then you reset the firmware and re-enroll your SB keys or disable it completely.
egorfine 1/28/2026||
> re-enroll your SB keys

This is possible only temporarily.

egorfine 1/28/2026|||
> we try to make every new feature that might be disruptive optional in systemd and opt-in

I find it hard to believe. Like, at all. Especially given that the general posture of your project leader is the exact opposite of that.

> systemd a healthy project

I can see that we share the same view that there are indeed differences in opinion.

egorfine 1/28/2026|||
> will the maintainer of systemd use their position to push this on everyone

Can you imaging the creator of systemd not to?

trueismywork 1/27/2026||
systemd is the most well supported init systemd there.
kelnos 1/28/2026||
Frankly this disgusts me. While there are technically user-empowering ways this can be used, by far the most prevalent use will be to lock users/customers out of true ownership of their own devices.

Device attestation fails? No streaming video or audio for you (you obvious pirate!).

Device attestation fails? No online gaming for you (you obvious cheater!).

Device attestation fails? No banking for you (you obvious fraudster!).

Device attestation fails? No internet access for you (you obvious dissident!).

Sure, there are some good uses of this, and those good uses will happen, but this sort of tech will be overwhelmingly used for bad.

UltraSane 1/28/2026||
Trusted computing and remote attestation is like two people who want to have sex requiring clean STD tests first. Either party can refuse and thus no sex will happen. A bank trusting a random rooted smartphone is like having sex with a prostitute with no condom. The anti-attestation position is essentially "I have a right to connect to your service with an unverified system, and refusing me is oppression." Translate that to the STD context and it sounds absurd - "I have a right to have sex with you without testing, and requiring tests violates my bodily autonomy."

You're free to root your phone. You're free to run whatever you want. You're just not entitled to have third parties trust that device with their systems and money. Same as you're free to decline STD testing - you just don't get to then demand unprotected sex from partners who require it.

alextingle 1/28/2026||
But I'm not having sex with my bank.
UltraSane 1/28/2026||
You do know what analogies are, right?
kmbfjr 1/28/2026|||
So both consent to sex and now one thinks they're entitled to marriage. That's where this inevitably leads, user/customer lock-in and control.

While the bank use case makes a compelling argument, device attestation won't be used for just banks. It's going to be every god damned thing on the internet. Why? Because why the hell not, it further pushes the costs of doing business of banks/MSPs/email providers/cloud services onto the customer and assigns more of the liabilities.

It will also further the digital divide as there will be zero support for devices that fail attestation at any service requiring it. I used to think that the friction against this technology was overblown, but over the last eighteen months I've come to the conclusion that it is going to be a horrible privacy sucking nightmare wrapped in the gold foil of security.

I've been involved in tech a long, long time. The first thing I'm going to do when I retire is start chucking devices. I'm checking-out, none of this is proving to be worth the financial and privacy costs.

UltraSane 1/28/2026||
"It's going to be every god damned thing on the internet. Why? Because why the hell not"

This is not a persuasive argument.

You are also ignoring the fact that YOU can use remote attestation to verify remote computers are running what they say they are.

"I've been involved in tech a long, long time. The first thing I'm going to do when I retire is start chucking devices. I'm checking-out, none of this is proving to be worth the financial and privacy costs."

You actually sound like you are having a nervous breakdown. Perhaps you should take a vacation.

mrguyorama 1/28/2026|||
A fundamentally flawed way to make an argument?

Yeah I know what analogies are.

Why does my bank need to know whether the machine in my hands that is accessing their internet APIs was attested by some uninvolved third party or not?

You know we used to hand people pieces of paper with letters and numbers on them to do payments right? For some reason, calling up my bank on the phone never required complicated security arrangements.

TD Bank never needed to come inspect my phone lines to ensure nobody was listening in.

Instead of securing their systems and working on making it harder to have your accounts taken over (which by the way is a fruitful avenue of computer security with plenty of low hanging fruit) and punishing me for their failures, they want to be able to coerce me to only run certain software on my equipment to receive banking services.

This wasn't necessary for banking for literally thousands of years.

Why now? What justification is there?

A third party attesting my device can only be used to compel me to only use certain devices from certain third parties. The bank is not at all going to care whether I attest to it or not, they are going to care that Google or Microsoft will attest my device.

And for what? To what end? To prevent what alleged harm?

In what specific way does an attested device state make interacting with a publicly facing interface more secure?

It WILL be used to prevent you from being able to run certain code that benefits you at corporation's expense, like ad blockers.

Linux is supposed to be an open community. Who even asked for this?

UltraSane 1/29/2026||
"Why does my bank need to know whether the machine in my hands that is accessing their internet APIs was attested by some uninvolved third party or not?"

Because there are an infinite ways for a computer to be insecure and very few ways for it to be secure.

Checks were a form of attestation because they contained security features that banks would verify.

Would YOU be willing to use a bank that refused to use TLS? I didn't think so. How is you refusing to accept remote attestation and the bank refusing to connect to you any different?

tliltocatl 1/28/2026|||
You are trying to portrait it as an exchange between equal parties which it isn't. I am totally entitled not to have to use a thrid-party-controlled device to access government services. Or my bank account.
UltraSane 1/28/2026||
remote attestation is just fancy digital signatures with hardware protected secret keys. Are you freaking out about digital signatures used anywhere else?
tliltocatl 1/28/2026||
Trusted computing boil down to restricting what software I'm allowed to run on hardware I own and use. The technical means to do so are irrelevant.
UltraSane 1/28/2026||
"Trusted computing boil down to restricting what software I'm allowed to run on hardware I own and use." Remote attestation doesn't do this.
tliltocatl 1/28/2026||
It absolutely does. Emphasis on use. The last thing I need is my bank requiring me to use a Poettering-certified distribution because anything else is "insecure".
UltraSane 1/28/2026||
You are acting very entitled thinking you can dictate the conditions under which you can connect to other people's computers. This is a "it takes two to tango" situation. I'm sure YOU would refuse to connect to any bank that refuses to use TLS.
tliltocatl 1/28/2026||
No man, there is no tango. "It takes two" doesn't apply when one part is a huge corporation.
UltraSane 1/29/2026||
BOTH parties have to agree on the conditions under which the computers will connect and EITHER can reject them.
blueflow 1/28/2026||
> You're just not entitled to have third parties trust that device with their systems and money.

But its a bank, right? Its my money.

UltraSane 1/28/2026||
If malware on your phone steals it the bank could be on the hook. The bank can set terms on how you access their computers.
blacklion 1/28/2026||
Can it sets terms on my religious and political views? I'm not speaking about race and sex, you cannot choose them (ok, sex you could in some jurisdictions, and there is difference between sex and gender, please, don't be nitpicky here), but about things I can choose same as I can choose my hardware and software to run.

If there is real effective market (which is not in any country on Earth, especially for banks), you could say: vote with you money, choose bank which suits you. But it is impossible even with bakery, less with banks on market which is strictly regulated (in part as result of lobbying by established institutions, to protect themselves!).

So, on one hand, I must use banks (I cannot pay for many things in cash, here, where I live most of bars and many shops doesn't accept cash, for example, and it is result of government politics and regulations), and on other hand banks is not seen as essential as access to air and water, they could dictate any terms they want.

I see this situation completely screwed.

UltraSane 1/28/2026||
You DO understand you can own more than one phone, right? Just use one that isn't rooted as a dedicated banking device and the rooted phone for whatever else you need. You are making life far too hard.
blacklion 1/28/2026||
But to have two desktop computers — one attestable and other not — is much more hard than two mobile devices.

And we are discussing this movement here. You know, пive him an inch and he'll take a yard.

UltraSane 1/29/2026||
It is actually very easy to use VMs for the non attesting machine.

Would YOU be willing to use a bank that refused to use TLS? I didn't think so. How is you refusing to accept remote attestation and the bank refusing to connect to you any different?

kfreds 1/27/2026||
1. Are reproducible builds and transparency logging part of your concept?

2. Are you looking for pilot customers?

esseph 1/27/2026|
Damn, you are thirsty!

Are these some problems you've personally been dealing with?

kfreds 1/27/2026|||
I just want more trustworthy systems. This particular concept of combining reproducible builds, remote attestation and transparency logs is something I came up with in 2018. My colleagues and I started working on it, took a detour into hardware (tillitis.se) and kind of got stuck on the transparency part (sigsum.org, transparency.dev, witness-network.org).

Then we discovered snapshot.debian.org wasn't feeling well, so that was another (important) detour.

Part of me wish we had focused more on getting System Transparency in its entirety in production at Mullvad. On the other hand I certainly don't regret us creating Tillitis TKey, Sigsum, taking care of Debian Snapshot service, and several other things.

Now, six years later, systemd and other projects have gotten a long way to building several of the things we need for ST. It doesn't make sense to do double work, so I want to seize the moment and make sure we coordinate.

phatfish 1/28/2026||
This appears to be the only comment worth reading. Thanks.
MomsAVoxell 1/27/2026|||
These kinds of problems are very common in certain industries.
Thaxll 1/27/2026||
I always wondered how this works in practice for "real time" use cases because we've seen with secure boot + tpm that we can attest that the boot was genuine at some point in the past, what about modifications that can happen after that?
Nextgrid 1/28/2026|
A full trusted boot chain allows you to use a reboot to revert back to a trusted state after suspected runtime compromise.
redleader55 1/27/2026||
Can you share more details at this point about what you are trying to tackle as a first step?
blixtra 1/27/2026||
As per the announcement, we’ll be building this over the next months and sharing more information as this rolls out. Much of the fundamentals can be extracted from Lennart’s posts and the talks from All Systems Go! over the last years.
dTal 1/27/2026|||
I'm sorry, you're "happy to answer questions" and this is your reply to such a softball? What kind of questions will you answer? Favorite color?
warkdarrior 1/27/2026|||
> Favorite color?

As per the announcement, we’ll be building a favorite color over the next months and sharing more information as it rolls out.

ingohelpinger 1/28/2026|||
lol
vaylian 1/28/2026|||
Probably also some of the things that were described here? https://0pointer.net/blog/fitting-everything-together.html
Vinonasg 1/28/2026||
Remote attestation only works because your CPU's secure enclave has a private key burned-in (fused) into it at the factory. It is then provisioned with a digital certificate for its public key by the manufacturer.
antrlll19 1/28/2026||
Great; how can I short it?
lofaszvanitt 1/28/2026|
The photos depict these people as funny hobbits :D. Photographer trolled them big time. Now, the only question left is whether their feet are hairy.

---

Making secure boot 100 times simpler would be a deffo plus.

2b3a51 1/28/2026|
I'm not seeing any big problems with the portraits.

Having said that, should this company not be successful, Mr Zbyszek Jędrzejewski-Szmek has potentially a glowing career as an artists' model. Think Rembrandt sketches.

I look forward to something like ChromeOS that you can just install on any old refurbished laptop. But I think the money is in servers.

More comments...