Make "HOME" directory configurable for certstore and registry about freerdp HOT 8 CLOSED

@mfleisz I fail to see, except very customized embedded OSs, where HOME wouldn't be set.

What is the use case in this issue?

If this is very specific to embedded stuff (which I am affected as well) I'd prefer to move this to 1.1 if noone objects.

from freerdp.

Not just embedded systems will cause problems - no Windows-based system has "HOME" set by default. In it's current state the core is unusable on anything other than a non-embedded *nix platform as it simply crashes when getenv("HOME") fails.
It's hard for me to estimate how much effort it is going to be to have a clean fix. Maybe at least we can find a solution where certstore silently fails and the core is still able to connect to the server?

from freerdp.

Yes, windows is indeed a problem. The urgency of this issue depends if we're going to support Windows for 1.0 or not.

from freerdp.

@otavio: I did some work over the last couple of days to push the Windows port forward. I'll handle the configurable home issue, if it's not for Windows, it'll be for something else. ~/.freerdp is usually good for Linux and the BSDs, but then when you get out of those it's usually case by case for what's preferred.

from freerdp.

...and pushed.

Now if you set settings->home_path to something other than NULL (NULL by default), both the certstore and registry will use that value instead of calling getenv("HOME").

from freerdp.

Thx Marc-Andre, however the fix is not complete - get_local_certloc (called from x509_verify_cert in crypto.c) is still using getenv("HOME") (and later on seg faulting in strlen if HOME is not set) ...

from freerdp.

@mfleisz: now it should be fixed as well

from freerdp.

Awesome - thx :)

from freerdp.