Jump to content

Recommended Posts

Posted

Dear Support

We extended our contract with Serif, and the same license keys for the Affinity suite were maintained. However, the license has stopped working anyway.

We deploy the Affinity Suite on macOS using the Affinity.defaults file. My guess is that we need a new signature key in the file. 

Is there any way the requirement for the signature could be removed? I have noticed that if you deploy the appropriate key and email to /Users/<CURRENTUSER>/Library/Group\ Containers/6LVTQB9699.com.seriflabs/Affinity\ (Photo|Publisher|Designer)/license.xml, the licensing works, but it is not ideal to have to push files into user spaces on macOS due to privacy permissions issues, so we would rather avoid doing that if possible.

The above means that the signature key serves no absolutely no security purpose, so the requirement for a new signature key each time we renew the license seems pointless work both for Serif and for us.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.