browscap.org now supports HTTPS. This patch changes the Browscap URLs from HTTP to HTTPS. I tested it.
HTTPS should be more secure. HTTP is vulnerable to man-in-the-middle attacks. It seems unlikely, but an attacker could inject malicious Browscap data to exploit a vulnerability in the INI parser, or exploit some other vulnerability.
I also changed some URLs in the README.txt to HTTPS.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | browscap-6.x-2.x-switch_urls_to_https-2573711-6.patch | 1.73 KB | aohrvetpv |
| browscap-7.x-2.x-switch_urls_to_https.patch | 2.04 KB | aohrvetpv |
Comments
Comment #3
gregglesCommited to 7.x-2.x. Thanks!
Comment #4
aohrvetpv commentedThanks, I am porting to D6.
drupal_http_request()apparently doesn't validate HTTPS certificates :(, so this change wouldn't protect much against MITM. But this change is probably still a step in the right direction.Comment #5
aohrvetpv commentedChanged a few links on the project page to HTTPS for consistency with the READMEs.
Comment #6
aohrvetpv commentedPlanning to go ahead and commit.
Comment #8
aohrvetpv commentedNote that this will not work for PHP compiled without SSL support. SSL support is not listed as a requirement for running Drupal. I do not know if there are such PHP deployments in practice.