Bug 5601 - Client customizer for Mac client
Summary: Client customizer for Mac client
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Pierre Ossman
URL:
Keywords:
Depends on: 5659
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-05 09:06 CEST by Samuel Mannehed
Modified: 2018-05-29 11:07 CEST (History)
2 users (show)

See Also:
Acceptance Criteria:


Attachments

Description Samuel Mannehed cendio 2015-08-05 09:06:54 CEST
Currently we only have a client customizer for the Windows client. We should look into making one for Mac OS as well for example.
Comment 1 Henrik Andersson cendio 2015-09-21 08:50:40 CEST
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.
Comment 2 Henrik Andersson cendio 2015-09-30 16:37:06 CEST
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.
Comment 3 Henrik Andersson cendio 2015-09-30 16:37:55 CEST
(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 4 Pierre Ossman cendio 2018-05-29 11:07:29 CEST
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.

Note You need to log in before you can comment on or make changes to this bug.