So Apple&#x27;s had 14 years to work with OpenSSH, and instead chose to break sandboxing?

Deprecated since Mountain Lion. <a href="https:&#x2F;&#x2F;issuetracker.google.com&#x2F;40474030" rel="nofollow">https:&#x2F;&#x2F;issuetracker.google.com&#x2F;40474030</a><p>It’s what Apple experimented with before they came up with the current entitlements system.

&gt; sshd(8): On OS X SDK &gt;= 27, sandboxing is no longer supported as the API we depended upon has been removed and no obvious alternative provided.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;openssh&#x2F;openssh-portable&#x2F;commit&#x2F;d4b4c304a202f5099f2f60be9af9ba266212bb74" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;openssh&#x2F;openssh-portable&#x2F;commit&#x2F;d4b4c304a...</a>

They mention a donation link: <a href="https:&#x2F;&#x2F;www.openbsd.org&#x2F;donations.html" rel="nofollow">https:&#x2F;&#x2F;www.openbsd.org&#x2F;donations.html</a><p>I wonder what their funding is like.

I think this is much healthier approach to AI reports than curl has. But I understand both sides.

&quot;
* We have seen a number of cases where a security bug identified
* by AI tools is subsequently independently discovered by a
* different researcher. This suggests that adversaries who do not
* report bugs to OSS projects are likely to be able to discover
* these bugs too. Given this, the OpenSSH team will, for now, be
* making more frequent releases to get bugfixes into users&#x27; hands
* more quickly rather than batching them until the next planned
* release.&quot;

Really glad to see the rate of security fixes speeding up.