home.social

#log4j2 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #log4j2, aggregated by home.social.

  1. LLM slop bug reports in log4J2

    This thing now needs to be fixed on the highest level possible
    Wasting programmers time is what the LLMs are doing

    github.com/apache/logging-log4

    #log4J2 #LLM #AI #generated #Slop #bug #bounty #reports #technology #OpenSource

  2. LLM slop bug reports in log4J2

    This thing now needs to be fixed on the highest level possible
    Wasting programmers time is what the LLMs are doing

    github.com/apache/logging-log4

    #log4J2 #LLM #AI #generated #Slop #bug #bounty #reports #technology #OpenSource

  3. LLM slop bug reports in log4J2

    This thing now needs to be fixed on the highest level possible
    Wasting programmers time is what the LLMs are doing

    github.com/apache/logging-log4

    #log4J2 #LLM #AI #generated #Slop #bug #bounty #reports #technology #OpenSource

  4. LLM slop bug reports in log4J2

    This thing now needs to be fixed on the highest level possible
    Wasting programmers time is what the LLMs are doing

    github.com/apache/logging-log4

    #log4J2 #LLM #AI #generated #Slop #bug #bounty #reports #technology #OpenSource

  5. LLM slop bug reports in log4J2

    This thing now needs to be fixed on the highest level possible
    Wasting programmers time is what the LLMs are doing

    github.com/apache/logging-log4

    #log4J2 #LLM #AI #generated #Slop #bug #bounty #reports #technology #OpenSource

  6. I started working for @log4j in 2009 and made its last 1.2 series release. Since then, a lot has changed, but the community is still alive and growing. Proud of that!

    logging.apache.org/blog/2023/1

    #opensource #java #log4j #log4j2

  7. I started working for @log4j in 2009 and made its last 1.2 series release. Since then, a lot has changed, but the community is still alive and growing. Proud of that!

    logging.apache.org/blog/2023/1

    #opensource #java #log4j #log4j2

  8. I started working for @log4j in 2009 and made its last 1.2 series release. Since then, a lot has changed, but the community is still alive and growing. Proud of that!

    logging.apache.org/blog/2023/1

    #opensource #java #log4j #log4j2

  9. I started working for @log4j in 2009 and made its last 1.2 series release. Since then, a lot has changed, but the community is still alive and growing. Proud of that!

    logging.apache.org/blog/2023/1

    #opensource #java #log4j #log4j2

  10. I started working for @log4j in 2009 and made its last 1.2 series release. Since then, a lot has changed, but the community is still alive and growing. Proud of that!

    logging.apache.org/blog/2023/1

    #opensource #java #log4j #log4j2

  11. [#LOG4J2-3211] Remove support for Lookups in messages - ASF JIRA issues.apache.org/jira/plugins
    gitbox.apache.org/repos/asf?p=

    なんでそんなバッサリ削除できるような不要な機能つけたのか?><;

  12. Yoshi Yamaguchi(twitter.com@ymotongpoo)さんがツイートしました:

    Google Cybersecurity Actionチームによるlog4j2の脆弱性(CVE-2021-44228)の概要と取るべき対応、およびGoogle Cloudで行った対応とユーザーで行うべき確認についてのまとめ記事です。広く共有いただくためRTいただけると幸いです。 #gcpug #gcpja #log4j2

    t.co/r7pB5yhiQM
    twitter.com/ymotongpoo/status/

  13. Coucou les #chatons ! On nous signale dans l'oreillette une faille dans la lib java log4j. Plus d'info sur notre forum pour connaître les services #chatons pouvant être impactés. #log4jshell #Log4j2
    forum.chatons.org/t/log4j-java

  14. Coucou les #chatons ! On nous signale dans l'oreillette une faille dans la lib java log4j. Plus d'info sur notre forum pour connaître les services #chatons pouvant être impactés. #log4jshell #Log4j2
    forum.chatons.org/t/log4j-java

  15. RT @[email protected]

    In the wake of the Apache #Log4j2 vulnerability (CVE-2021-44228), we have shipped Docker Desktop 4.3.1, which includes updates to the docker scan command. More from CTO @[email protected] on what we know so far and how to know if you've been impacted: dockr.ly/3DM74Hm

    🐦🔗: twitter.com/Docker/status/1469

  16. RT @[email protected]

    In the wake of the Apache #Log4j2 vulnerability (CVE-2021-44228), we have shipped Docker Desktop 4.3.1, which includes updates to the docker scan command. More from CTO @[email protected] on what we know so far and how to know if you've been impacted: dockr.ly/3DM74Hm

    🐦🔗: twitter.com/Docker/status/1469

  17. RT @[email protected]

    Glad to see the quick action from the @[email protected] team, helping the community detect the #log4j2 vulnerability in their images with "docker scan"

    Well done 👏👏👏 twitter.com/stefscherer/status

    🐦🔗: twitter.com/felipecruz/status/

  18. RT @[email protected]

    Glad to see the quick action from the @[email protected] team, helping the community detect the #log4j2 vulnerability in their images with "docker scan"

    Well done 👏👏👏 twitter.com/stefscherer/status

    🐦🔗: twitter.com/felipecruz/status/

  19. RT @[email protected]

    It doesn’t matter if you like Java or not. We’re here to help each other in the community. If you want to check your #Docker images for #log4j2 vulnerabilities, update to the latest @[email protected] Desktop 4.3.1 which helps you with `docker scan` to find them.

    🐦🔗: twitter.com/stefscherer/status

  20. RT @[email protected]

    It doesn’t matter if you like Java or not. We’re here to help each other in the community. If you want to check your #Docker images for #log4j2 vulnerabilities, update to the latest @[email protected] Desktop 4.3.1 which helps you with `docker scan` to find them.

    🐦🔗: twitter.com/stefscherer/status