Comment by jpitz

5 hours ago

Uname is not enough here to identify what has or has not been done to your system to deal with the compromised certificates.

3 comments

jpitz

Reply
davidcollantes  5 hours ago

No, no, I meant it to show that the machine is running the current/latest macOS, and the results I am getting from curl on the two URLs.

  • microtonal  4 hours ago

    Maybe you have another curl in your path?

        $ uname -a
    Darwin MacBook 27.2.0 Darwin Kernel Version 27.2.0: Wed Oct 14 23:47:21 PDT 2026; root:xnu-13432.41.4~25/RELEASE_ARM64_T6030 arm64 arm Darwin
    $ which curl
    /usr/bin/curl
    $ curl https://dv-g3b-emudhra.we-have-a-problem.com/
    Your client successfully connected to the site. That's bad!

    • davidcollantes  4 hours ago

      Aha! Touche! Indeed, I am using brew's curl ("/opt/homebrew/opt/curl/bin/curl"). That's why; the one at "/usr/bin" connects just fine (facepalm).