Comment by ransom1538
6 hours ago
"Hey claude this is the cve I need you to fix [link]"
Takes about 20 seconds. Depending if you need to hit enter.
6 hours ago
"Hey claude this is the cve I need you to fix [link]"
Takes about 20 seconds. Depending if you need to hit enter.
cool cool cool. Don't understand what you're doing, and keep not understanding what you're doing. the agents are infallible after all, and who cares about properly verifying certs anyway? that's nerd shit.
We're in October 2026. Updating packages is the easiest thing Claude can do. For me, I asked and received:
Node 26.3 → 26.12.1 Homebrew’s CA bundle, certifi and OpenSSL are updated, and so are Python 3.13 and 3.14 (3.13.17 and 3.14.9). uv 0.10.9 → 0.13.5. python.org Python 3.13: pip 26.2.2, installed from PyPI’s wheel with its checksum checked, then certifi 2026.10.19.
It also checked some of the other recent vulnerabilities like LiteLLM (already updated).
Sure, and by outsourcing this simple thing, you're just a little more complacent. Someday, when it does something silly, you won't notice.
It went OK this time. There's no guarantee that it'll go OK every time, for every thing.
All I'm saying is that understanding how to maintain the systems that you are responsible for maintaining is an important thing, and outsourcing that understanding is very dangerous.
Yeah, at some point I gave up and asked AI to do patching for me. It was a good call because it found affected certificates in places where I wouldn't look (e.g. aws-cli or Libre Office).