Pinned Tweet
"We cannot solve our AI problems with the same level of AI we used when we created them" - A. I . Einstein
Jawaid Bazyar retweeted
Replying to @toshipepe
Programming, Motherfucker
programming-motherfucker.com…
Jawaid Bazyar retweeted
Open-source "codes of conduct" are cancer and need to be retired; I deeply regret championing them. The inevitable outcome is an unproductive mob controlling projects through intimidation. Given enough time, it pushes away people who would contribute patches. Eventually, all that remains is an unproductive military-police class playing social status games.
that's like not even one TV Show.
FIVE CENTS PER GIGABYTE. Lollercoaster.
xitter.gq/unusual_whales/status/…
(The entire cost of a gigabyte of data in the USA is 1/100 that amount...)
Jawaid Bazyar retweeted
Great line from the CTO of Proton. I’m paraphrasing and stealing it :
Your job is not to use agents to help you write code. Your job is to lead the agents to help them write code.
If you're into retro demo scenes at all, check out Deater's work. It's a lot of fun.
In case you missed it last year, here's "Monster Splash" a Halloween-themed demo for the Apple IIe
youtube.com/watch?v=2cab1ovv…
Jawaid Bazyar retweeted
Sesame Streets Count von Count getting the contracting call for the single digit secret.
Announcing 3 Critical vulns for hundreds of millions of IoT, Firewalls, OT, and Military devices including: Palo Alto Networks, Comcast, D-Link, HP, Canon, Honeywell, GE, Oracle, Siemens, Rockwell, Digi, Lockheed Martin, Boeing...
The vulns are with GoAhead Web Server which is a backend library used by these devices. There's a patch available from GoAhead but that doesn't mean there's a patch available for the devices yet -- that's up to the manufacturer.
- TLS traffic over DHE ciphers have a 1-byte secret, "04", meaning anyone can decrypt connections to these devices and steal login credentials and session tokens if the client negotiated with DHE ciphers like the latest TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256, which is extremely likely.
- LibreSSL mTLS has been completely bypassed, meaning anyone can connect over mTLS. If you have one of these devices listening on the internet and are expecting mTLS to protect it from attackers, take it offline or patch asap.
- OpenSSL Certificate Revocation Lists (CRLs) are not enforced, meaning if a user device is stolen or compromised, and you revoke that mTLS cert, nothing actually happens. There are a lot of other attacks this can be used for.
These are critical because these types of devices run our world. Water systems, electricity, military, firewalls, critical infrastructure.
foxio.io/blog/choose-your-ba…
Jawaid Bazyar retweeted
Replying to @LundukeJournal
Interesting idea. Popping off the stack certainly matches a lot of code shapes, and is far faster than doing malloc/free all the time.
I always thought it was a shame that modest default stack setups made alloca() a generally-frowned-upon technique in C/C++. With 64 bit architectures, give every stack a virtual address space equal to the physical memory by default!
You can do a surprisingly good job of memory management with just the stack, and I contend that it has both correctness and performance advantages.
Allocations are a trivial pointer adjustment, and frees are literally free. Keeping everything linearly packed is friendlier for all layers of the cache hierarchy, and it makes keeping everything in huge / gigantic pages easy.
Leaving temporary intermediate blocks on the stack can seem wasteful, but unless you are dealing with algorithms that make > O(n) temporary allocations, it is usually not a big deal.
Static analysis can check if you store a stack pointer into a structure deeper in the stack, which is a use-after-free, and then memory management correctness is guaranteed.
The discipline of caller-allocates-return is awkward in some dynamic cases. It would take a change in low level calling conventions, but you could plausibly have functions that return with the stack extended from where it was when they were called. I’m not holding my breath for that.
It isn’t obvious if having AI coding agents makes discussions of software architecture more or less important!
If you're not using AI to secure your software, be assured someone is using AI to find the vulnerabilities in your software.
Jawaid Bazyar retweeted
The lesson for GRANITE Act:
Refusal *works.* Making refusal of a foreign censorship order easy, and guaranteeing legal consequences to a foreign censor in a US court, will result in foreign censorship orders ceasing to enter the United States.




















