Most of those "empanelled" firms end up being spokespersons of the establishment, only to retain their empanelment status, and safeguard their contracts & revenue.
Real cybersecurity situation with most institutions & firms in India is unbearably uncomfortable. And nobody cares.
I once criticized CERT-In on LinkedIn and got calls from terrified employers (past & then present) asking me to remove it.
I said no and proceeded to change all my employment history to ‘Confidential’ to ease their worries.
The reason they panic is because they don’t want to lose their “CERT-In Empanelment”.
CERT-In Empanelment is one of the biggest scams in the Indian cyber security industry.
CERT-In makes you go through several stages of tests (all worthless btw) and then “certifies” you as an empaneled auditing firm.
This status then allows you to bid on government contracts for cyber security projects along with enabling you to serve compliance customers under regulatory bodies.
If, for whatever reason, CERT-In decides to revoke this empanelment, the firm would lose majority of its business.
That’s how CERT-In keeps all the major cyber security firms in India under their thumb.
1
40
Prima facie, details posted by @ni5arga seem valid.
Bigger concerns:
1. no competent private firm would validate, as they fear retribution by GoI, impacting business/revenue
2. many competent independent researchers have seen GoI filing criminal cases, just to silence them
11
Okay this is __HUGE__!!!
ni5arga.com/blog/posts/hacki…
Hey @ni5arga, can you open your DM please!
20
Well, pam_fingwit has a pretty easy LPE bug.
github.com/xapp-project/fing…
(Security issue: Local Privilege Escalation in pam_fingwit)
This one needs physical access to the machine, but the impact is way too high!
1
1
56
Looks like there are many on the same lines!
github.com/search?q=%22execv…
20
If you are using an ISP other than Airtel or Jio in India, your Ecovacs robot might not be able to reach ecovacs.com due to buggy filtering at Ecovacs portal, thus rendering your robot unuusable.
Issues started after 24Mar2026.
Hey @ecovacsrobotics, @excitel_rocks
ecovacs.com (resolves to all.ecovacs.com.a1.initww.co…) isn't reachable from a few ISPs like Excitel in India.
Excitel resolves that to 43.109.97.45 & times out, whereas Airtel resolves to 155.102.2.162 & works.
Check your DNS!
51
It's sorta amusing to find that many are discovering now that version-pinning* is a great way to save oneself from cybersec disasters.
*was once an almost mandatory thing, in places with a decent safety-first programming culture, at least till 2015.
ZIRP & YOLO era ruined it!😂
Today is another package-lock.json appreciation day!
- Make sure you always commit your project with the package-lock.json file. It is the ONLY version locking enforcement mechanism.
- Use npm ci instead of npm install. The first one will work ONLY if package-lock.json exists.
- If you need to update or pull new packages, use the --min-release-age flag (available since npm v11.10.0) to make sure you only install updates, which are at least 7 days old:
npm install --min-release-age=7
Or hardcode this setting into your .npmrc file:
min-release-age=7
There will be more malicious updates to popular npm packages in the future, driven by supply chain attacks. It's just the beginning.
Thankfully, they will be caught in the first 24 hours.
The npm ecosystem is broken by design.
Adapt and act accordingly.
Stay safe out there!
1
2
393
Claude finds an RCE in vim; older vim is immune!
Imagine an seeker who can run Claude against all popular FOSS, in parallel on their many used/popular versions, and build out a DB of exploits that work across many versions of an app.
Remember K3yM4k3r from Matrix Reloaded!😂
We asked Claude to find a bug in Vim. It found an RCE. Just open a file, and you’re owned. We joked: fine, we’ll switch to Emacs. Then Claude found an RCE there too.
Full story: blog.calif.io/p/mad-bugs-vim…
47
Hey @ecovacsrobotics, @excitel_rocks
ecovacs.com (resolves to all.ecovacs.com.a1.initww.co…) isn't reachable from a few ISPs like Excitel in India.
Excitel resolves that to 43.109.97.45 & times out, whereas Airtel resolves to 155.102.2.162 & works.
Check your DNS!
@excitel_rocks recheck your BGP peering!
Took 100 samples each, dig on ecovacs.com via 8.8.8.8, 8.8.4.4 & 1.1.1.1. Resolves to { 43.109.97.22, 43.109.97.31, 43.109.97.45, 43.109.97.52 }
@ecovacsrobotics These aren't reachable from Excitel ISP (ASN: 133982)
48
Rashtrotthana folks @Rashtrotthana_P,
Maybe you deserve a better IT partner. Seems your current IT partner isn't really doing even basic site monitoring properly.
Please reach out via DM for more details! I can help in setting up some basic site monitoring for your portal.
21
A popular core banking solution also depends on a large C & C++ base. Similar rules are enforced to ensure sanity of the maintainers. Additional checks to keep the cyclomatic complexity under a limit (at class/file/function levels), limits on macros, no recursion etc.
NASA writes mission-critical flight software in C.
And the rules are absolutely INSANE.
> No recursion. Ever.
> Every loop must have a provable upper bound.
> No dynamic memory allocation after initialization.
> Max ~60 lines per function.
> Minimum 2 assertions per function.
> Every return value must be checked.
> Zero compiler warnings allowed.
> Daily static analysis. Zero warnings there too.
> No function pointers.
> Restricted pointer dereferencing.
This is how they write code at NASA / JPL for mission-critical systems.
50
Almost every AWS offering has that sweet zone where price-performance both aren't prohibitive. As needs scale or as use-cases change, the cost-to-value starts getting skewed.
Good FinOps would catch such changes early on and help in finding alternatives to save costs.
I reduced my cloud bill from +$8000/m to ~$900/m.
The two biggest AWS cost drivers:
- Database and compute.
And it's such an easy cost trap to avoid.
If I had to start over today, there is *one* service I would prioritize the highest:
DynamoDB.
For years, I thought DynamoDB was both brilliant and convenient.
- Schemaless
- Serverless
- Cheap
What's not to like?
Well, turns out, it's only cheap for a while. And the schemaless nature of DynamoDB quickly starts working against you...
Instead, I ditched DynamoDB and went with some boring old tech.
Let me explain 👇
17
Sanity & limited-time-on-Earth are precious.
One must use specialist tools to
- automate the "call candidate -> run questions -> collect answers" loop
- simplify the SitRep gathering workflow
- manage various pipelines (scheduling, nudging, follow-up etc)
Automate & prosper!
1
183
>> Rather than throw hardware at the problem, our engineering team relied upon thoughtful architecture
Neat!
There are many tech leaders that get fooled by the "merchants of complexity", over-engineering their solutions at the infra layer.
cc: @dhh @brankopetric00 @QuinnyPig
2 servers.
8 CPUS.
Processing 8 billion ticks per day. Under 2 milliseconds.
Running at 20% CPU utilization.
Sometimes the best infrastructure is the one you build yourself.
That's our market feed data infrastructure at Sahi. This processes high speed feeds from the Exchanges and builds the critical data products that power your trading experience on Sahi.
Rather than throw hardware at the problem, our engineering team relied upon thoughtful architecture choices:
→ Lock-free Rust actors
→ Pre-serialized message caching
→ Time-bucketed partitioning
→ Token-aware database routing
Full technical deep-dive:
sahi.com/blogs/from-exchange…
@Sahi_HQ
1. Learn "Just in time learning"
2. Build stuff in public. Don't bother about perfection.
3. Have a video portfolio of projects, discussions etc. In 202X, if you can't create content, you'll be out of the game.
4. High-quality "networks" are very rare in India. Choose cautiously.
Replying to @23aryansharma11
1. Get your fundamentals right.
2. Network for long term.
3. Be well spoken, mild mannered.
4. Improve your articulation skills.
5. side projects are extremely helpful in early career, it allows you to showcase your learning ability, interest and agency.
6. Learn the art of marketing yourself.
7. Be visible in social media - if you can.
1
23
While there will be a few disasters when many vibecode home automation solutions, it's still a great overall win for the home automation ecosystem.
Users can now design workflows according to their life, instead of aligning their life around a workflow dictated by some corp.
I was inspired by this so I wanted to see if Claude Code can get into my Lutron home automation system.
- it found my Lutron controllers on the local wifi network
- checked for open ports, connected, got some metadata and identified the devices and their firmware
- searched the internet, found the pdf for my system
- instructed me on what button to press to pair and get the certificates
- it connected to the system and found all the home devices (lights, shades, HVAC temperature control, motion sensors etc.)
- it turned on and off my kitchen lights to check that things are working (lol!)
I am now vibe coding the home automation master command center, the potential is 🔥.And I'm throwing away the crappy, janky, slow Lutron iOS app I've been using so far. Insanely fun :D :D
23
Restuarant Chain mental model to understand the basics of k8s ecosystem is very helpful for many.
Source: medium.com/@kanishks772/i-wi…
9
A "k8s is a type system for Infra" perspective makes a lot of sense.
Let's hope similar to evolution of proglangs, this domain also evolves for the better, offering alternatives that are much more intuitive and simpler for the practitioners.
Replying to @zhoro_x
every time I entertain that idea my mind is blown, but it's the most accurate model I came up with for thinking about k8s
think about this for a few minutes: kubernetes provides you with a type system for managing your infrastructure
much like a programming language does, but instead of integers, characters and strings, you get services, deployments and pods
and just like in a programming language you can have custom types in the form of CRDs
every single thing you have in your cluster is wrapped in a type and that's very important because it makes it very clear what is running inside the cluster and what it can do
combined with a runtime whose job is to continuously reconcile your declared resources (each with its own type btw) into actual workloads
that's the moat of kubernetes
it's not the container orchestration part and it never has been
10
Sounds highly suspicious.
1. If there's really nothing to hide, why make a huge fuss wasting precious founder energy & effort, instead of simply trashing that *black*mail?
2. If LEA are already on it, why announce in public & share a status update with the blackmailers?
This quoted post is unavailable.
282

























