Octoprint, because it does not specify a CA bundle anywhere, falls back to the default Python CA bundle. This prevents a user from adding a trusted CA, and being able to use that for connections from Octoprint.
This change lets Octoprint fall back to use the Debian/Raspbian default CA bundle - so that users can update the CA certificates for the OS (and not have to find other options to figure out how to separately change Python's CA cert bundle.
Octoprint, because it does not specify a CA bundle anywhere, falls back to the default Python CA bundle. This prevents a user from adding a trusted CA, and being able to use that for connections from Octoprint.
This change lets Octoprint fall back to use the Debian/Raspbian default CA bundle - so that users can update the CA certificates for the OS (and not have to find other options to figure out how to separately change Python's CA cert bundle.