| 2011-03-11 02:23:05 |
Olaf Meeuwissen |
description |
More automatic printer driver download feedback. This follows up from #733023. Note that this is concerned with downloaded drivers from third party repositories using their own GPG keys.
Once GPG has been made proxy aware, there is still the problem that many proxy configurations only let traffic through for ports 80 (HTTP) and 443 (HTTPS). GPG HTTP keyservers by default listen on 11371 (HKP). During our tests we had our IT department punch a temporary hole for that port for us but that isn't a viable solution.
In the jockey sources, the default is set to keyserver.ubuntu.com which operates on the default HKP port. I don't know if it's possible to override this is a configuration file somewhere but I think pointing the default keyserver to one that operates on port 80 (or 443) will prevent a lot of frustration.
We, for one, had quite a bit of trouble just getting those temporary holes punched for testing purposes :-| |
More automatic printer driver download feedback. This follows up from #733023. Note that this is concerned with downloaded drivers from third party repositories using their own GPG keys.
Once GPG has been made proxy aware, there is still the problem that many proxy configurations only let traffic through for ports 80 (HTTP) and 443 (HTTPS). GPG HTTP keyservers by default listen on 11371 (HKP). During our tests we had our IT department punch a temporary hole for that port for us but that isn't a viable solution.
In the jockey sources, the default is set to keyserver.ubuntu.com which operates on the default HKP port. I don't know if it's possible to override this in a configuration file somewhere but I think pointing the default keyserver to one that operates on port 80 (or 443) will prevent a lot of frustration.
We, for one, had quite a bit of trouble just getting those temporary holes punched for testing purposes :-| |
|
