[gdal-dev] GDAL, Proj and cacert

[Greg Troxel]

Howard Butler <howard at hobu.co> writes:

>> On Feb 11, 2022, at 1:41 PM, Jeff McKenna <jmckenna at gatewaygeomatics.com> wrote:
>> 
>> Unfortunately this issue comes up very often, as you said, so much
>> of our stack relies heavily on environment variables.  My hope is
>> that in the long run, the ini-style of settings can help battle this
>> Windows Server x64 issue (yes googling this does return many
>> unproven/non-reproducible reports for other projects, very
>> disheartening).
>
> The frustrations of how to pass environment variables in different
> computing environments is an issue that's orthogonal to how GDAL
> expresses configuration through environment variables. I get that the
> rules of environment variable resolution can be quite bespoke
> depending on the computing platform and environment you are operating
> on, but it's not legit to say "environment variables don't always work
> for me, we should do config files, but I don't have a reproducible
> test case to show that"

Also, it strikes me that the root cause of the problem is that if one
wants certain trust roots to be accepted for validation, then the right
thing is to change the system configuration accordingly.    It is a sign
of misconfigured systems that we are even talking about accomodations
within GDAL.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20220211/07fca4c9/attachment.sig>