I have tried uninstalling, rebooting, and reinstalling the client but my password is still not encrypted. Is there something I have to do to get it to work?
Ok, after an absolute nightmare time getting an XP VM installed (if you don't keep focus on the VM console during install, it will hang at the device install portion), then installing 87 googolplex windows updates, here's what I found.
With WinXP Pro 32-bit, I can replicate this bug. On this OS, the Password string value in HKEY_CURRENT_USER\Software\Astaro\Astaro Authentication Client\ is not encrypted and is still displayed in plain text.
This also leads to another bug with AAA in XP. Because the value is not encrypted, but AAA.exe is expecting it to be, AAA.exe doesn't/can't pre-populate the password for set credentials if the client is restarted. Every time the client is restarted, the password needs to be entered again.
Here's my analysis on why this is happening. I could be far off on this, but it's what it looks like to me given the information available. Looking at the value in Vista and Win7, it appears that part of the encryption process is converting the password characters to an asian character set. In Vista and Win7, all languages are available to the OS by default. In WinXP (2003 and 2000 also), only the default language is available, so the language translation portion of the encryption process fails.
__________________ ACE v8/SCA v9.3
...still have a v5 install disk in a box somewhere.
Scott, could you also install IPv6 stack on XP (that's the easy part).... then you need Dibbler to be able to install an IPv6 DHCP client on XP otherwise it can only use announcements to get an IP. I'm hoping you can replicate my other issue which is in another thread called https://community.sophos.com/products/unified-threat-management/astaroorg/f/110/t/71009 .
Scott, could you also install IPv6 stack on XP (that's the easy part).... then you need Dibbler to be able to install an IPv6 DHCP client on XP otherwise it can only use announcements to get an IP. I'm hoping you can replicate my other issue which is in another thread called https://community.sophos.com/products/unified-threat-management/astaroorg/f/110/t/71009 .