3 ms·

Chrome already blocks self signed certs out of the box.

• rgbrenner 11y ago
  ... and then you click the "Advanced" link and click on "Proceed to x.x.x.x (unsafe)"
  • exelius 11y ago
    Not always - some "unsafe" cipher combinations it will simply refuse to load with no workaround. Though you usually only see this on dodgy IoT gadgets out of China/Korea.
    • jfoster 11y ago
      I've encountered that a bunch of times. I understand needing to make it look dangerous and deterring people who don't know what they are doing from continuing, but it's silly of Chrome not to offer any way of proceeding for people who do know for certain that they want to.
  • arenaninja 11y ago
    Unlike FF, Chrome doesn't offer an option for a permanent exception once you click "Proceed to ..."
    • veemjeem 11y ago
      if you're on a mac, you can add the cert to your keychain and then all your dev sites that operate over *.dev will be fine.
      • arenaninja 11y ago
        > if you're on a mac Thanks. I know about that, but I am not on a mac.
    • cheald 11y ago
      I recently set up a self-signed cert for a development site, and Chrome remembered it until I told it to forget it (so I could install a CA-signed cert).
      • deleted 11y ago
        [deleted]
    • notatoad 11y ago
      It does, just not on the warning page like ff does. You can install your self-signed cert in the settings panel.
  • chc 11y ago
    This gets rather tedious after a few dozen times.