nobody confident in their own abilities is panicking
-
@jackryder @Viss @da_667 Even the fact that everything runs on GPOSs like Windows because it's easy is bad. Keep it fucking simple. Why should orgs have to mitigate so many vulns in services they don't want and don't need? Because it's easier for "engineers?" GTFO.
@cR0w @jackryder @Viss @da_667 Because it’s easier to support if everything is installed and turned on by default. You don’t get pesky users calling saying, “Why isn’t this working?” Fewer support calls saves money.
We were fighting this battle in the OS during my Center for Internet Security days back in the early 2000s and made some progress as far as default installs. But entropy is gonna entropy.
-
nobody confident in their own abilities is panicking
Infosec community panics over Anthropic Claude Code Security
ai-pocalypse: Not the first of its kind
(www.theregister.com)
the people who are panicking are signaling.
@Viss What I am not confident in is the ability of tech CEOs to prioritize delivering products that are not pure shit.
Delivering quality vs. delivering pure crap at a much lower cost?
-
nobody confident in their own abilities is panicking
Infosec community panics over Anthropic Claude Code Security
ai-pocalypse: Not the first of its kind
(www.theregister.com)
the people who are panicking are signaling.
@Viss The real victims here are the juniors and people recently entering a new field. LLMs teach you nothing (you have to do the learning yourself, like you always do), yet they give the illusion of productivity. The game is rigged so that junior devs are rewarded for pretending to gain understanding, when all they do is lean on the LLMs and hope they don’t fuck up.
-
nobody confident in their own abilities is panicking
Infosec community panics over Anthropic Claude Code Security
ai-pocalypse: Not the first of its kind
(www.theregister.com)
the people who are panicking are signaling.
@Viss Hey now, Claude found an SQL injection in my code and I like to think I have a pretty good practice of secure coding.
It thinks the statically typed i32 is an injection vulnerability and wants to fix it with more than a hundred lines of crud because it doesn’t understand how to make parameterized statements in my SQL library. It also made all of that crud public API in ways it could easily be called out of order and make new state issues. But that’s exactly the point.
-
if youve ever been burned because some asshole in HR shitcanned your resume because "you didnt go to the right college" or you couldnt score a gig because "you refused to get a cissp", or if youve ever ragequit a job because you were just "the token security person who was only there to fulfill a checkbox, and nobody listened to you and you felt like your job didnt matter" then you should want it to burn down too
@Viss When I got into security something like 15 years ago, it was so different. At that time, in the Mac community, I could make a difference, and do meaningful things. That’s so much harder to do now, with so many stupid, bureaucratic roadblocks, and I’m glad I’m looking at a career in the security industry in the rear view mirror.
-
@cR0w @da_667 thats another big angle too
2 years ago at securityfest i was at lunch and another presenter showed up. some js/npm guy. he laughed and gloated that he doesnt ever need to give a shit about the network or the OS because who cares? his js shit works and thats all that mattered. he openly flaunted being ignorant about how the shit that makes his entire world function is lame and he doesnt care about it.
its that kinda sentiment right there, that installs the rot
@Viss @cR0w @da_667 People who have contempt for everything outside of their overengineered virtual machine really grind my gears, because when their abstraction inevitably leaks, this sclerotic industry will prevent them from suffering the consequences of their actions. But I ran into people like this ten years ago. LLMs just kicked the dilettantism into hyperdrive.
-
@catsalad surely it would be (kernel)panic at the cisco
@Viss "Oh you know IOS? Which one–the fruit or the trash fire?"
-
-
@Viss Panic! At the Infosec?
-
nobody confident in their own abilities is panicking
Infosec community panics over Anthropic Claude Code Security
ai-pocalypse: Not the first of its kind
(www.theregister.com)
the people who are panicking are signaling.
@Viss getting supremely annoyed at that headline and how much bullshit it's carrying
-
if youve ever been burned because some asshole in HR shitcanned your resume because "you didnt go to the right college" or you couldnt score a gig because "you refused to get a cissp", or if youve ever ragequit a job because you were just "the token security person who was only there to fulfill a checkbox, and nobody listened to you and you felt like your job didnt matter" then you should want it to burn down too
Don't hold back Viss. Tell us how you really feel.
But seriously, to the point of the original article, yeah, no.
If I'm being very generous and allow that a "spicy linter" might be a halfway decent SAST (static application security testing) tool, that best case scenario would still be overwhelmed by the new and interesting security bugs introduced by their code generating brethren, "spicy autocomplete."
Full agree with Viss on the main point about folks with deep technical view.
-
nobody confident in their own abilities is panicking
Infosec community panics over Anthropic Claude Code Security
ai-pocalypse: Not the first of its kind
(www.theregister.com)
the people who are panicking are signaling.
@Viss on but I will panic, just not for the reasons they think.
-
nobody confident in their own abilities is panicking
Infosec community panics over Anthropic Claude Code Security
ai-pocalypse: Not the first of its kind
(www.theregister.com)
the people who are panicking are signaling.
@Viss the people who might be panicking for good reason are software maintainers at companies where thes agents are going to be given free range to fix usually inconsequential yellow flags by inserting reams of unreviewed code.
-
nobody confident in their own abilities is panicking
Infosec community panics over Anthropic Claude Code Security
ai-pocalypse: Not the first of its kind
(www.theregister.com)
the people who are panicking are signaling.
apropos
Shafik Yaghmour (@shafik@hachyderm.io)
@carnage4life@mas.to What does it mean to modernize COBOL? The problem of why we have COBOL has nothing to do w/ COBOL itself. It is because there is zero cost incentive to port these core but totally working systems. Changing any of these systems would create way more systematic risk than any value you would gain by replacing the systems themselves. It is the same reason why any legacy system is hard to replace. Same goes for FORTRAN in the science community. Could you replace, yes of course you could. Can you be sure it will replicate all the decades of papers that were written using that software ¯\_(ツ)_/¯ Does anyone have the incentive or money to figure it out, NO! Why are we listening to any of these people, they are talking nonsense.
Hachyderm.io (hachyderm.io)
-
@Viss the people who might be panicking for good reason are software maintainers at companies where thes agents are going to be given free range to fix usually inconsequential yellow flags by inserting reams of unreviewed code.
@kevingranade then the leadership of those companies are going to suffer quite largely when all their engieers quit, and their product catches fire, and all their customers leave.
-
apropos
Shafik Yaghmour (@shafik@hachyderm.io)
@carnage4life@mas.to What does it mean to modernize COBOL? The problem of why we have COBOL has nothing to do w/ COBOL itself. It is because there is zero cost incentive to port these core but totally working systems. Changing any of these systems would create way more systematic risk than any value you would gain by replacing the systems themselves. It is the same reason why any legacy system is hard to replace. Same goes for FORTRAN in the science community. Could you replace, yes of course you could. Can you be sure it will replicate all the decades of papers that were written using that software ¯\_(ツ)_/¯ Does anyone have the incentive or money to figure it out, NO! Why are we listening to any of these people, they are talking nonsense.
Hachyderm.io (hachyderm.io)
@shafik there will be, at some point, enough people willing to deal with the pain of moving off ancient stuff like that. it may suck at first, but it will basically have to happen at some point because nobody is exactly teaching fortran and cobol these days, so soon as those engineers age out, the shit becomes egyptian heiroglyphs
-
@cR0w @Viss @da_667 I've had that convo!
"We don't have resources to do it safely" is such a strange take for an organization that exists in the real world.
Timelines suck, vendors are charming, shareholders have crazy requests. It's a terrible cycle.
But cheating the cycle is lazy and just erodes the efforts of others.
@jackryder @Viss @da_667 Part of the problem is how many stakeholders are involved with every decision, including upstream and unaffiliated with your own org. It's maddening and difficult since it's gotten so out of hand.
-
@shafik there will be, at some point, enough people willing to deal with the pain of moving off ancient stuff like that. it may suck at first, but it will basically have to happen at some point because nobody is exactly teaching fortran and cobol these days, so soon as those engineers age out, the shit becomes egyptian heiroglyphs
It is basically already like that, I think Vernor Vinge got it right. If we are still around ages from now it will be layers and layers of legacy code no one understands all the way down.
It is a very interesting thought process for someone who is in the depths of software development in big tech to really plan out what such a long term migration would look like just for one company. Once you get it, it is very humbling to realize how hard it really is.
-
It is basically already like that, I think Vernor Vinge got it right. If we are still around ages from now it will be layers and layers of legacy code no one understands all the way down.
It is a very interesting thought process for someone who is in the depths of software development in big tech to really plan out what such a long term migration would look like just for one company. Once you get it, it is very humbling to realize how hard it really is.
I am also read "Thinking in Systems" and it is a good book to read if you are thinking about this kind of stuff:
Shafik Yaghmour (@shafik@hachyderm.io)
Reading “Thinking in Systems” “Purposes are deduced from behavior, not from rhetoric or stated goals” We often get stuck on what is said and forget to look at results. If the results never match what is said then you need to realize maybe what is said is meant to mislead. It could also be lack of skills but that is not much better.
Hachyderm.io (hachyderm.io)
-
@cR0w @jackryder @Viss @da_667 Because it’s easier to support if everything is installed and turned on by default. You don’t get pesky users calling saying, “Why isn’t this working?” Fewer support calls saves money.
We were fighting this battle in the OS during my Center for Internet Security days back in the early 2000s and made some progress as far as default installs. But entropy is gonna entropy.
@hal_pomeranz @jackryder @Viss @da_667 Fair. We're so far into it that it's almost impossible to fight that one with a reasonable amount of resources. But it's still frustrating. It's the part of the whole "microservices" or "serverless" that I like. You don't have to inherit a bunch of dependencies and vulnerabilities the same way you would if you had to spin up a Windows or RHEL or Ubuntu machine just for your simple needs.
I chime in with a "Haven't you people ever heard of commenting your goddamn code? No..."
