Jonkman Microblog
  • Login
Show Navigation

  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Conversation

Notices

  1. lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Sunday, 20-Feb-2022 12:47:58 EST lnxw48a1 lnxw48a1
    A member of the #log4j team talks about #log4shell and their patching process https://therecord.media/the-apache-log4j-team-talks-about-the-log4shell-patching-process/ [therecord media]

    He's clearly been coached in avoiding making any sensational or upsetting statements. I wish more of us got such coaching.
    In conversation Sunday, 20-Feb-2022 12:47:58 EST from nu.federati.net permalink

    Attachments

    1. Invalid filename.
      The Apache Log4j team talks about the Log4Shell patching process
      from The Record by Recorded Future
      The Record spoke with Christian Grobmeier, a member of the Apache Logging team and one of the developers who maintain the Log4j library.
    1. GeniusMusing (geniusmusing@nu.federati.net)'s status on Sunday, 20-Feb-2022 13:09:03 EST GeniusMusing GeniusMusing
      in reply to
      @lnxw48a1
      All it takes is a team of PR people and lawyers...

      I keep waiting for some stupid company to start a suite against FOSS for something like this regardless of the most used line in FOSS licenses, "THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED...".

      Not that I really want to see this.
      In conversation Sunday, 20-Feb-2022 13:09:03 EST from nu.federati.net permalink
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.

Switch to desktop site layout.