there seems to be some major problems with the installation process on a swedish windows xp. this seems to be due to the fact that the administators group in "swedish" spells "administratörer" and
analogously "users" spells "användare". these special characters "ä" and "ö" does not seem to go down well with the installation scripts. i was only able to work around this by manually entering the lines from setperms.cmd, while substituting the variables with the above values, into a cmd.exe window.
another issue i had was that the contents of the /var directory were left at rwxrwxrwx, which also prevented sshd from starting. not sure if this is related to the first problem, though.
anyway, all this can be applied after the installation is run. all you have left to do is to reboot or start the OpenSSH service manually.
That problem will be fixed in the next release. Meanwhile, specifying the localized names in quotes would be a good idea (setperms.cmd):
"C:\Program Files\copssh\bin\subinacl" /noverbose /subdirectories "C:\Program Files\copssh\*" /setowner="%LISTACC_ADMGROUP%" > NUL
"C:\Program Files\copssh\bin\xcacls" "C:\Program Files\copssh" /T /G "%LISTACC_ADMGROUP%":F /Y > NUL
..
"C:\Program Files\copssh\bin\xcacls" "C:\Program Files\copssh" /T /E /G "%LISTACC_USRGROUP%":R /Y > NUL
...
net localgroup "%LISTACC_ADMGROUP%" SvcCOPSSH /add
That problem will be fixed in the next release. Meanwhile, specifying the localized names in quotes would be a good idea (setperms.cmd):
sorry that won't work. .cmd scripts just can't handle 'exotic' characters. quotes won't help. one way might be to find an install system that doesn't rely on cmd scripts. maybe .vbs?
another way is to find other commands to achieve the same results, and that takes SID's as input instead of regular group names. both the Users and the Administrators groups have fixed SID's (http://support.microsoft.com/kb/243330). SetACL (http://setacl.sourceforge.net/index.html) can replace xcacls and subinacl i believe. how to replace net localgroup i don't know, maybe .vbs anyway.
meanwhile i'll keep on typing the commands by hand for new installs:
each of these lines goes into the cmd prompt one by one. xcalcs generates some errors, but in the end, everything works anyway.
"C:\Program\copssh\bin\subinacl" /noverbose /subdirectories "C:\Program\copssh\*" /setowner=Administratörer > NUL
"C:\Program\copssh\bin\xcacls" "C:\Program\copssh" /T /G Administratörer:F /Y > NUL
"C:\Program\copssh\bin\xcacls" "C:\Program\copssh" /T /E /G SvcCOPSSH:F /Y > NUL
"C:\Program\copssh\bin\xcacls" "C:\Program\copssh" /T /E /G Användare:R /Y > NUL
"C:\Program\copssh\bin\chmod" 755 /bin
"C:\Program\copssh\bin\chmod" 755 /etc
"C:\Program\copssh\bin\chmod" 755 /var
"C:\Program\copssh\bin\chmod" 755 /home
"C:\Program\copssh\bin\chmod" 775 /tmp
"C:\Program\copssh\bin\chmod" 600 /etc/ssh_h*
"C:\Program\copssh\bin\chown" SvcCOPSSH /var/empty /var/run /etc/ssh_h*
"C:\Program\copssh\bin\chown" SvcCOPSSH /var/empty /var/run /etc/ssh_h*
net localgroup Administratörer SvcCOPSSH /add
after this i still have to correct permissions in /var/*:
"C:\Program\copssh\bin\chmod" 755 /var/*
then reboot or manually start the OpenSSH service.
Thank you for your feedback. Highly appreciated. I am aware of the weaknesses of the installation script when it comes to support for localized windows.
Nowadays, I prepare copSSH 1.4.0. It will use a perl-based admin program to automate all the command-line based functionality. Localized names will be addressed as well.
Version 1.4.0 will be released within a couple of weeks.
did some more digging, seems like nsis can handle both of the problematic tasks (acl and localgroup) using:
http://nsis.sourceforge.net/AccessControl_plug-in
and
http://nsis.sourceforge.net/User_Management_using_API_calls#Add_User_to_...
i'd be happy to trya and help with a fix, but of course, i'm $129 short :|
so i'm looking forward to 1.4.0