Implementing Signed updates first time

Hi Wyatt, 

Thanks for the app once again.

I have (stupidly) never been doing signed updates and I am now realising it.

I understand in Properties is Sign Updates.

I always include the latest  client file in my updates.

Is the process as easy as ticking sign updates and then the new Client file will have the signature.

Then from there on they will always check for the same sig?

So my current users (400) will update fine using the current client with no sign, but then the NEW client will be expecting signing, thus its a very simple process?

I mean, I would assume this is teh case, but obviously I don't want to screw up a 400 client roll out.

Hello,

I understand that if you did not include the signature and now you include it, since neither the public nor the private key matches, the update will not be downloaded. You will need to deploy an updated installer executable with the new package configuration and its signature, to avoid any problems.

Reply
Discard post