≡

wincent.dev

  • Products
  • Blog
  • Wiki
  • Issues
You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.
Home » Issues » Bug #228

Bug #228: Upon restart, registered app is no longer verified.

Kind bug
Product Synergy Advance
When Created 2005-05-06T22:53:47Z, updated 2005-05-12T03:37:49Z
Status closed
Reporter Ryan Edwards
Tags no tags

Description

Each time I restart my G4, when I would start up Synergy Advance, the app was no longer verified as registered. So I unregistered it, multiple times, and re-inputted the reg. code. Now I have exceeded my registration limit.

Comments

  1. Ryan Edwards 2005-05-06T23:00:51Z

    Here's the pop-up I now get on starting up Synergy Advance: "The activation request was denied by the server. The reason for the denial was, "Activation limit (total activations) exceeded"."

  2. Greg Hurrell 2005-05-07T00:11:37Z

    Try downloading the new version. I will reset your activation limit.

    When you activate the software, the following activation certificate is written to your ~/Library/Preferences folder:

    com.wincent.SynergyAdvance.activation.certificate.plist

    Keep a backup of that file, just in case.

  3. Greg Hurrell 2005-05-11T21:06:53Z

    Thanks for your collaboration on this one, Ryan. In response to the data you collected I've changed the activation algorithm. Adding the "fixed-in-prerelease" keyword. I will put out a 0.1.2 release shortly that contains the changes.

    For others who may be reading this and don't know the back story, it appears that on Ryan's machine Cocoa was returning inconsistent NSFileSystemNumber values across reboots. Not totally random but variable. His machine was returning three different numbers (let's call them x, y and z) and returning x on some reboots, y on others and z on others. It's not clear to me why this was happening on his machine (and one other user has reported the same issue) but regardless of the underlying cause I think this warrants the modification of the algorithm.

    I've made changes to the activation algorithm so that it no longer users the NSFileSystemNumber. As I said in an email to Ryan, it doesn't seem to be a very useful number anyway from a mathematical point of view. In other words, it doesn't possess a lot of "uniqueness"; the number returned by my own system and others that I have found by searching on Google are all within a few units of each other. From a security perspective I don't think the NSFileSystemNumber adds anything at all to the algorithm. So out it goes.

    Sorry to anyone who was inconvenienced by this issue.

  4. Greg Hurrell 2005-05-12T03:37:49Z

    0.1.2 is now on the servers.

Add a comment

Comments are now closed for this issue.

  • contact
  • legal

Menu

  • Blog
  • Wiki
  • Issues
  • Snippets