Page MenuHome GnuPG

gpg4win CLI installation ignores .ini configuration
Open, Needs TriagePublic

Description

as tested with versions 4.4.0 and 5.0.0-beta, the silent CLI installation currently seems to ignore the configuration as provided by /C=%SOMEPATH%\config.ini and always installs the default components. allthough the component flags in src/nsis/inst-sections.nsi include also the components currently in development, configuring them in the .ini file has no effect.

the likely cause for this was mentioned in T7452#195896 and a forum comment ("config_ functions have not been ported from ascii to unicode").

Event Timeline

Thanks for opening the ticket. I looked at it when it was reported in the forum, But had no test build at hand to test a fix. If you look at the history of g4wihelp.c you can see how other functions have been ported to Unicode recently. The change is that the strings in the nsis script world have changed to two byte strings. The problem is then where the c code interacts with the NSIS script obtaining parameters and setting return values. Since the popstackna takes an ascii string it only takes the first character as the second byte is null. Changing these occurrences to popstackn and the setuservariable to widechar should do the trick.