Error 0: RegOpenKeyEx when importing acl.txt

[icestorm50]

I'm using the latest 104RC14 and am trying to upload the ACL I have used in the past

allow 0x00000003 BUILTIN\Administrators

and I am getting this error when I run mslogonacl.exe /i /o c:\acl.txt

Error 0: RegOpenKeyEx
deleting ACE_data linked lists

once this is done the acl inside the program is still empty
does anyone know what I am doing wrong?
Thanks,
Erick

[PCDSmartie]

Same problem here with version 1.0.5 and shipped MSLogonACL.exe (x86/x64) in 64 Bit and 32 Bit commandline interpreter.

>MSLogonACL.exe /i /o acl.txt
account: VORDEFINIERT\Administratoren, mask: 3, type: allow
Detected domain = DOMAIN
account: DOMAIN\Domõnen-Admins, mask: 3, type: allow
Error 0: RegOpenKeyEx
deleting ACE_DATA linked lists

Same problem with one entry:

>MSLogonACL.exe /i /o acl.txt
account: VORDEFINIERT\Administratoren, mask: 3, type: allow
Error 0: RegOpenKeyEx
deleting ACE_DATA linked lists

Any ideas?
Thanks in advance.

[Malzbier]

Hello PCDSmartie,

i had the same problem with the empty "UltraVNC Security Editor" dialogue when using "MSLogonACL.exe" to import security settings for a silent installation on multiple machines.

The solution was to manually create the key "HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3" first and importing the security settings with MSLogonACL.exe afterwards.

Obviously MSLogonACL.exe is unable to create this key independently and when it doesn't find it it simply does nothing.
I think this is a relict of former times when UltraVNC stored it's settings in the registry.

mfg
M. Metzger

[PCDSmartie]

Hi Malzbier,

I need this for creating a new MSI-file, but with this information I will create the old regkeys and will test. Thank you.

[Malloc]

I can confirm that this is still an issue.

As mentioned above, if I create the registry keys first, then the import works fine. This bug should be resolved.

As a workaround, I added this command before I use MSLogonACL.exe
REG ADD HKLM\Software\ORL\WinVNC3

[char1iecha1k]

Hi

I was looking for somewhere suitable to post this and I found this thread.

To fix this problem replace lines 228 to 233 in vncImportACL.cpp from this

Code: Select all

if (ERROR_SUCCESS != RegOpenKeyEx( HKEY_LOCAL_MACHINE,
   _T("Software\\ORL\\WinVNC3"),
   0, KEY_SET_VALUE, &hk )){
   _ftprintf(stderr, _T("Error %d: RegOpenKeyEx\n"), GetLastError());
   __leave;
}

to this

Code: Select all

if (ERROR_SUCCESS != RegCreateKeyEx( HKEY_LOCAL_MACHINE,
   _T("Software\\ORL\\WinVNC3"),
   0, NULL, 0, KEY_SET_VALUE, NULL, &hk, &dwDisposition )){
   _ftprintf(stderr, _T("Error %d: RegOpenKeyEx\n"), GetLastError());
   __leave;
}

and add this above the try catch

Code: Select all

DWORD  dwDisposition;

from msdn http://msdn.microsoft.com/en-us/library/ms838625.aspx

Before you can read or write to a key, you must first obtain a handle to it. To do this, use either the RegOpenRegKeyEx or RegCreateKeyEx Microsoft Win32 functions. In practice, you will almost always use RegCreateKeyEx, which will open the key if it exists or create it if it does not. Here is a typical scenario:

I have uploaded a compiled version here

http://www.mediafire.com/file/nk4zznzn1yz/MSLogonACL.exe

and the source here

http://www.mediafire.com/file/2mlenyignwm/vncImportACL.cpp

[sutex]

I just fixed it. Helpful to me.

Hi

To fix this problem replace lines 228 to 233 in vncImportACL.cpp from this

[redge]

Rudi

user reported that this fix is not updated to ultravnc since 20.03.2010 !!!!
http://www.mediafire.com/file/2mlenyign ... ortACL.cpp
please add the fix asap for 1.0.9.5.1

[duncan]

Thanks char1iecha1k for your effort. The fix did not work for me though. I'm thinking I'm going to have to deploy it with out Windows authentication

[Jodiazio]

duncan, I don't know why it didn't work for you but the solution works fine

[ppstay]

I am having the same problem here on Win7 64bit with 1.1.9 x64. Weird thing is I don't have this problem on another same win7 machine. Even after I manually created the registry key HKLM:\Software\ORL\WinVNC3. This is driving me crazy. Any workaround? Any help would be appreciated.

[ppstay]

OK. I figured it out, on 64 bit version the registry path is under Wow6432Node. Once run the following before import, it could succeed.

REG ADD HKLM\Software\Wow6432Node\ORL\WinVNC3