Replying to @mat_benwell @HackingDave
Good security is always a layered approach.
A configurable WAF with frequent updates or Cloudflare in front with front-door origins blocked would considerably mitigate a lot of these.
Patches are one approach, but not the only one.
1
7
splitXCH retweeted
Earlier @grok estimate for a novel, non-fork @chia_project DEX: $200k–$700k+ to launch securely.
What a wizard actually shipped self-funded in spare time: The Forge (weighted N-asset AMM, CHIP-0062). Live on mainnet (V20 + V16), custom action-layer puzzles, multisig, first CAT-CAT pairs, full test suites, iterative reviews.
The expensive specialized engineering is already done. Next we will incentivize lp rewards to make a stronger tvl market as a community.
What was estimated out of reach is being done as @aWizardxch community.
Replying to @mat_benwell @HackingDave
Some of the recent ones have been
"We use it and an attacker can reach it but target-specific fingerprinting and attack chain customization are required, but work can be automated"
That's what I've pieced together from the social media chatter and limited leaks.
7
Replying to @JaredRyanSears
> Back in the 1960s, 5 people were paying into SS for every recipient. Today it is around 2.5. People are also living longer than they did in the past.
Says not a Ponzi scheme. Describes a late-stage Ponzi scheme. LMAO.
31
Replying to @willofzwest @HackingDave
Because a lot of vendors need extensive pressure to actually fix their fuck-ups
1
1
15
Replying to @mat_benwell @HackingDave
Would you rather they just release a general purpose executable exploit before a fix? That's where this line of thinking naturally takes us.
1
14
Replying to @vikphatak @HackingDave
Prudent approach, because I think we have some in each bucket recently
8
Replying to @maolius42 @HackingDave
Especially with open source, which I love and embrace, but you have to recognize its drawbacks. If I can obtain a version fingerprint remotely I can tune the whole attack chain iteratively off box and nearly silently on an identical version of source code with white box knowledge
5
Replying to @cryptodoge8 @CISACyber
I guarantee COBOL could be hacked. The protection it gets is from there being no modern, directly network-accessible systems. They are accessed by layers of shims and translation gateways that would be hacked before the COBOL ever needed to be touched.
Replying to @Sparkeysf @nickisanders
Interestingly, syslog over UDP is the only protocol I've personally seen fail in the way mentioned here. When an invalid forwarding target is encountered, a switch doesn't know who the UDP traffic is intended for and will start blasting it out all ports simultaneously.
16
Replying to @filipporiccio1 @robertgraham
From a design perspective, a hardened data type is always better than interacting with an unhardened data type "the right way" everywhere it is used. A lot of software is well past the design phase and you can only realistically hope to make incremental fixes though.
1
1
12
Replying to @gabsmashh
I just checked and they still remembered all my credit card balance. Better luck next time, hackers!
2
48



