Authorization problem with two devices

Submitted by vhuserclient on #1

I’m successfully working with the ClientAuthorization script with 1 device, using the proposed bash script. 

But when using it with 2 devices, it authenticates only on the first one. On the second, it sends a login attempt without a password. Both devices are configured with AUTO USE and both work correctly without using ClientAuthorization. 

I used 312b8a6c015b49e9.8993.9693 because it’s the one set to 1 by AUTO USE DEVICE.

VirtualHere Client IPC, below are the available devices:
(Value in brackets = address, * = Auto-Use)

Raspberry Hub (raspberrypi:7575) 
  --> 1000 (raspberrypi.31) 
  --> Mass Storage (raspberrypi.1212) 
 *--> Device 1 (raspberrypi.32) (In-use by you)
 *--> Device 2 (raspberrypi.1211) (In-use by you)

Auto-Find currently on
Auto-Use All currently off
Reverse Lookup currently off
Reverse SSL Lookup currently off
VirtualHere Client is running as a service

Below is the configuration

[General]
AutoUse=1
ReverseLookup=0
PresavedPasswords=312b8a6c015b49e9.32,root (root)\\**pwd**,312b8a6c015b49e9.8993.9693,root (root)\\**pwd**
[AutoShare]
PW003FP0.12561.9693=0
PW003FP0.12561.9693.15=0
PW003FP0.15=0
All=0
312b8a6c015b49e9=0
312b8a6c015b49e9.9044.9693.32=0
312b8a6c015b49e9.9044.9693=0
312b8a6c015b49e9.32=1
312b8a6c015b49e9.12561.9693.31=0
312b8a6c015b49e9.12561.9693=0
312b8a6c015b49e9.31=0
312b8a6c015b49e9.9044.9693.124=0
312b8a6c015b49e9.124=0
312b8a6c015b49e9.8993.9693.1211=0
312b8a6c015b49e9.8993.9693=1
312b8a6c015b49e9.1211=0
[Settings]
ManualHubs=1.2.3.4:7575
[Transport]
EasyFindId=X************tPsGcAv3aa
EasyFindPin=2****w

Submitted by Michael on Tue, 2025/10/21 - 10:42

#2

Did you manually edit the vhui.ini with the PresavedPaswords field?
 

Anyway the format is

<server serial>.<address>,password[,<server serial>.<address>,password]

However the second entry appears to have a USB Vendor ID and Product id instead of the address. This is why it doesnt work. Its not the correct format.

 

Submitted by vhuserclient on Tue, 2025/10/21 - 18:38

#3

no, the format was generated by the Windows executable. If I try to use the proposed format <server serial>.<address>,password[,<server serial>.<address>,password], the MD5 sent is not correct. Even when using the full address 312b8a6c015b49e9.8993.9693.1211,root (root)\\**pwd**, the same problem occurs.

Submitted by Michael on Tue, 2025/10/21 - 19:21

#4

Running the client as a service cannot ask for a password. It cannot show a password dialog box to ask the user.

So i assume you were running the client normally (not as a service) and clicked "Save Password" after you put in the correct one and then installed the client as a service? Is that the sequence? I cannot see how the second entry in the PresavedPasswords was generated. Its showing a VID/PID instead of an address.  

The second entry should be 312b8a6c015b49e9.1211,root (root)\\**pwd**

Try manually entering it like that and see if it works (note you can only edit the vhui.ini when the client service is not running)

Submitted by vhuserclient on Tue, 2025/10/21 - 19:47

#5

Thank you for the support. 

Using 312b8a6c015b49e9.1211,root (root)\**pwd** as the second entry works correctly.