Post B6ljkObE1xPIY9jFmy by jpm@aus.social
 (DIR) More posts by jpm@aus.social
 (DIR) Post #B6lca8T2SGhBwU3mxk by ariadne@social.treehouse.systems
       1 likes, 0 repeats
       
       this is not how you handle security disclosure #AISlophttps://github.com/pkgconf/pkgconf/pull/512
       
 (DIR) Post #B6lcp2tZSCwZ0La1bM by joshbressers@infosec.exchange
       0 likes, 0 repeats
       
       @ariadne "Exploitation scenario: An attacker creates a ..."It would be funny it wasn't so sad
       
 (DIR) Post #B6ld8zpmXputIoJxw0 by chrisvest@mastodon.social
       0 likes, 0 repeats
       
       @ariadne irresponsible disclosure and sneak-patching is so common now 🫩
       
 (DIR) Post #B6leyacVdR7w7BHJYm by jotak@framapiaf.org
       0 likes, 0 repeats
       
       @ariadne same bot opened a PR on one of my repos... False positive for me, but same kind of "irresponsible disclosure"
       
 (DIR) Post #B6lg3X8a6wdgiQCWiO by ariadne@social.treehouse.systems
       0 likes, 0 repeats
       
       @jotak it is basically a false positive, but i decided to go in a different direction to avoid other bots bothering me about it
       
 (DIR) Post #B6lgXxw52WrUW5rgi8 by ariadne@social.treehouse.systems
       0 likes, 0 repeats
       
       in case it was not obvious, the pkgconf project is intended to be interacted with by human operators only.i do not wish to argue with a pile of matrix multiplications
       
 (DIR) Post #B6ljkObE1xPIY9jFmy by jpm@aus.social
       0 likes, 0 repeats
       
       @ariadne thanks for finding another slop-extruded to block on GitHub