Hello, On Dec 6, 2010, at 6:32 PM, Viktor TARASOV wrote: > to reflect the commonly used template for the path to the windows registers > that the smart card producers are using Following the common practices of a platform is a good idea. Yet it sometimes feel there is too much unnecessary bloat in Windows :)
> ([HKEY_...]Software\[Manufacturer]\[ProductName]), > I would like to add one more level to the OpenSC windows registers path. > > To finally have: > RegOpenKeyEx(HKEY_CURRENT_USER, "Software\\OpenSC Project\\OpenSC", ... > instead of actual > RegOpenKeyEx(HKEY_CURRENT_USER, "Software\\OpenSC", ... HKLM vs HKCU is the only question for me. As on Unix OPENSC_CONFIG can be overridden from command line and so all tunables are user-modifiable, the default could be HKCU, then HKLM if HKCU key is not found. Certain options would be nice to make unmodifiable to the normal in the future (set by administrator, only from opensc.conf/HKLM or similar) but that's Does it actually change anything? The only *smart card* related entries under ...\Calais (or CSP descriptors, which don't matter for OpenSC) don't depend on the other parts of the registry. > What do you think? Fine, as long as it is documented and universally followed [1] As I'm (again) testing to see if the current codebase can be released as 0.12.0, so the change should be done ASAP so that the Windows environment description would be fixed before the non-conforming setups spread. [1] http://www.opensc-project.org/opensc/wiki/WindowsInstaller#PossibleinstallerstepsWindowsenvironmentdescription -- @MartinPaljak.net +3725156495 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
