@BenjaminHCCarr This. #infosec is hard even on mature, well seasoned, battle-tested technologies, so I am willing to give a pass to #foss developers who usually develop useful tools on their time and dime for all to use, especially when it comes to risks inherent to emerging technologies like #AI.
However, this case is interesting to me because it seems to me that the emerging technology -related risks have been more thoroughly thought out and protected against than the same old same old.
Credentials exposed in plaintext, lack of user and privilege separation, etc.
As a FOSS enthusiast and security guy, I do believe that FOSS developers do have a duty with their user base to produce as secure as possible software for all to use. Security is a core, though oft neglected aspect of software quality.
However, as a FOSS developer myself, although nothing on the scale of #clawdbot / #moltbot , I know security *is* hard. It requires time, resources and expertise that even many teams on big companies don't have. I'm not pointing fingers here.
Therefore I do believe that we, the security minded people in the FOSS community ( #FOSSSec if you'll indulge me) have a duty towards developers and users.
The most impactful way is obviously to just pr a fix imho. But at a systemic level just that won't work.
Much ink has been spilled on #securityawareness (tm), but I don't think the problem is that people aren't aware anymore.
It's a problem of improving security culture and habits, and one way we can do that is by improving the functionality and usability of existing FOSS security tools, so that more people learn and use them, for instance.