5 comments

  • K0IN4 hours ago
    related (and good writeup): <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=50378228">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=50378228</a>
  • brynet4 hours ago
    Damien Miller also provided some further details on openssh-unix-dev@: <a href="https:&#x2F;&#x2F;marc.info&#x2F;?l=openssh-unix-dev&amp;m=179388064263131&amp;w=2" rel="nofollow">https:&#x2F;&#x2F;marc.info&#x2F;?l=openssh-unix-dev&amp;m=179388064263131&amp;w=2</a>
  • SV_BubbleTime2 hours ago
    &gt; because we have recently observed multiple cases of rapid bug rediscovery by AI agents, sometimes within hours, and so now consider long embargo periods to be a dangerous practice that primarily benefits attackers.<p>Seems quite reasonable. It’s quite obvious that black hats have day jobs as White hats and have been privy to embargoes for probably decades.
    • InsidiousWombat1 hour ago
      Embargo should last at most to the moment fix is made and code passes test suite.<p>Anything longer is putting systems at danger. I can recompile the package with a patch (even if Ubuntu&#x2F;RHEL takes 3 weeks to do it) myself in a pinch, and I&#x27;d like to have a chance for it before the bug gets re-discovered by malicious party
      • tremon0 minutes ago
        What if the test suite passes in the middle of the night? Should all administrators interrupt their sleep and get up to recompile their servers immediately?
    • aomix2 hours ago
      I think this is a long held belief of the project and why they have been excluded from bug embargo’s in the past.
  • ChrisArchitect1 hour ago
    Some earlier discussion: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=50377221">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=50377221</a>
  • selckin6 hours ago
    See also <a href="https:&#x2F;&#x2F;hachyderm.io&#x2F;@damienmiller&#x2F;117563026759098135" rel="nofollow">https:&#x2F;&#x2F;hachyderm.io&#x2F;@damienmiller&#x2F;117563026759098135</a>