OpenSSH 10.6p2 Critical workaround for alpine without PAM

(openssh.org)

200 points | by selckin 8 hours ago

6 comments

  • K0IN 6 hours ago
  • brynet 6 hours ago
    Damien Miller also provided some further details on openssh-unix-dev@: https://marc.info/?l=openssh-unix-dev&m=179388064263131&w=2
  • ChrisArchitect 3 hours ago
  • SV_BubbleTime 4 hours ago
    > 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.

    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.

    • InsidiousWombat 3 hours ago
      Embargo should last at most to the moment fix is made and code passes test suite.

      Anything longer is putting systems at danger. I can recompile the package with a patch (even if Ubuntu/RHEL takes 3 weeks to do it) myself in a pinch, and I'd like to have a chance for it before the bug gets re-discovered by malicious party

      • tremon 2 hours 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?
        • stonogo 1 hour ago
          That is generally the practice in professional environments, yes. Many places have an on-call rotation, and those that don't soon discover why. An embargo wouldn't fix that particular problem anyway, because time zones exist.
          • Xylakant 43 minutes ago
            Also: There’s always midnight somewhere.
        • pgporada 1 hour ago
          [dead]
    • aomix 4 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.
  • selckin 8 hours ago
  • slukmbr 54 minutes ago
    [dead]