KosmicTask v1.1.1 Released

Content

KosmicTask v1.1.1 Released

Posted in:

Mugginsoft is pleased to announce the availability of KosmicTask v1.1.1 a secure Integrated Scripting Environment for OS X that makes it easy to share script based functionality over the network. For an introduction to the application and in depth help see the help book.

Changes Since Previous Version

This maintenance release address the following issues:

  1. MID 1157: Licence files can now only be installed for the current user not for all users.
  2. MID 1159: Fixed keychain issue which meant that a remote user was prompted to grant private key access by KosmicTaskServer when admin access was first requested.

Notes for MID 1157

Earlier versions of the application allowed admin users to install application licences so that they would be available to all users on the machine. In OS X 10.7 changes to the root Library folder permissions mean that this option is no longer viable.

Notes for MID 1159

Security is an important part of the KosmicTask design philosophy but that does not mean that it should compromise application usability. Security features should be robust, easily configurable and largely transparent. KosmicTask uses Transport Layer Security to ensure network privacy. When the application is first launched a unique identity (a certificate and private key pair) is generated and used to encrypt network traffic. The certificate was being imported with an incorrect access object which resulted in the user being prompted to allow access. This was especially troublesome as the user prompt was generated when remote admin access was first requested and no user may have been present to respond to the prompt.

Local KosmicTask communications (that is, between the client component and the task server) are not encrypted in order to preserve responsiveness for the local user. This explains why the keychain prompt was only generated when a secure remote connection was required (the server component requires access to the identity private key in order to successfully establish the TLS connection).