diff options
Diffstat (limited to 'net/py-urllib31/files')
| -rw-r--r-- | net/py-urllib31/files/patch-setup.cfg | 11 | ||||
| -rw-r--r-- | net/py-urllib31/files/pkg-message.in | 21 |
2 files changed, 32 insertions, 0 deletions
diff --git a/net/py-urllib31/files/patch-setup.cfg b/net/py-urllib31/files/patch-setup.cfg new file mode 100644 index 000000000000..8e92a5d7e5b8 --- /dev/null +++ b/net/py-urllib31/files/patch-setup.cfg @@ -0,0 +1,11 @@ +--- setup.cfg.orig 2024-08-29 15:36:43 UTC ++++ setup.cfg +@@ -7,7 +7,7 @@ universal = 1 + universal = 1 + + [metadata] +-license_file = LICENSE.txt ++license_files = LICENSE.txt + provides_extra = + secure + socks diff --git a/net/py-urllib31/files/pkg-message.in b/net/py-urllib31/files/pkg-message.in new file mode 100644 index 000000000000..4aa5b9e1f1d9 --- /dev/null +++ b/net/py-urllib31/files/pkg-message.in @@ -0,0 +1,21 @@ +[ +{ + message: <<EOM +Since version 1.25 HTTPS connections are now verified by default which is done +via "cert_reqs = 'CERT_REQUIRED'". While certificate verification can be +disabled via "cert_reqs = 'CERT_NONE'", it's highly recommended to leave it on. + +Various consumers of net/py-urllib3 already have implemented routines that +either explicitly enable or disable HTTPS certificate verification (e.g. via +configuration settings, CLI arguments, etc.). + +Yet it may happen that there are still some consumers which don't explicitly +enable/disable certificate verification for HTTPS connections which could then +lead to errors (as is often the case with self-signed certificates). + +In case of an error one should try first to temporarily disable certificate +verification of the problematic urllib3 consumer to see if that approach will +remedy the issue. +EOM +} +] |