Currently we only have a client customizer for the Windows client. We should look into making one for Mac OS as well for example.
Bug 3046 adds a configuration file to the application bundle. With this sites could customize and distribute their own ThinLinc client. However modifying the configuration will break the signature of the bundle and the end-user will be prompted with a dialog telling the application is damage with and option to move to trash i run by double click. To overcome this problem the end-user should right click and select open from context menu, this will bring a dialog where the user can open the application anyway. Opening the modified application bundle this way will add an exception and the signature of the application will not be verified for subsequential startups.
With implementation of bug 5659, ThinLinc client reads system wide configuration files from /Library/Application Support/ThinLinc Client. Here follows the steps to create a installation package with bundled configuration files for custom installation at sites: - Create a workdir structure as: mkdir -p ~/workdir/root/Library/Application\ Support/ThinLinc\ Client mkdir -p ~/workdir/root/Applications - Copy ThinLinc Client application bundle into root/Applications - Put customized tlclient.conf into root/Library/Application\ Support/ThinLinc\ Client - Build a custom installation package using following command: pkgbuild --root ~/workdir/root --ownership recommend ~/workdir/ThinLinc\ Client.pkg Now you can distribute the package installer placed in ~/workdir to be installed with custom configuration.
(In reply to comment #1) > Bug 3046 adds a configuration file to the application bundle. With this sites > could customize and distribute their own ThinLinc client. However modifying the > configuration will break the signature of the bundle and the end-user will be > prompted with a dialog telling the application is damage with and option to > move to trash i run by double click. To overcome this problem the end-user > should right click and select open from context menu, this will bring a dialog > where the user can open the application anyway. Opening the modified > application bundle this way will add an exception and the signature of the > application will not be verified for subsequential startups. This can be ignored now when bug 5659 is implemented.
Comment #2 solves the issue of customized configuration and ssh keys, but it does not solve the issue of branding as the image needs to be stored inside the bundle (breaking the signature). We probably need to move the branding to /Library/Application Support/ThinLinc Client as well.
