SB expiration date

[NewsArchive]

Hello,

still thinking of using SB for my installations...

How SB prevents for cracking a time limit installation or webupdate by setting
the system date back?

Thanks much and best regards

Kai

[NewsArchive]

My methods do not involve the installer. I include run times in the
application data files.

Steve

--
Neural Planner Software Ltd

http://www.easynn.com
http://www.tropheus.demon.co.uk

[NewsArchive]

Kai,

If you are using the built-in setupPROTECT subscription feature, a
manipulation of the system clock does not help your customers in any way.
If the subscription has expired and the customer is not qualified to receive
the new version (full install or update), the installer or web update does
not accept the (expired) subscription key.

Does this help?

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

By the way, of course, we are eating our own dog food <g>. SetupBuilder
itself is protected by this build-in subscription feature. If a
subscription key expired, it is impossible to install a new version/update.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hello Friedrich,

thanks for information. How do you have done this? Where do you get the real
date? From an internet clock/calender or the webserver?

When i use a date subscription i need to have a expire date. How the key can
expire when the customer set back the date ?

Thanks for help understanding.

Best regards Kai

[NewsArchive]

Kai,

> thanks for information. How do you have done this? Where do you get the
> real
> date? From an internet clock/calender or the webserver?
>
> When i use a date subscription i need to have a expire date. How the key
> can
> expire when the customer set back the date ?

The web update installer holds the compile date. Let us assume, a
subscription expired on 31-DEC-2007. You make a new web update available on
01-JAN-2008, today is the 06-JAN-2008. The customer receives a message that
a new version is available. But his subscription expired, so the web update
process reports that a new subscription is required in order to install the
update. Okay, your customer is smart enough to set back his system clock to
01-DEC-2007. But SetupBuilder's setupPROTECT feature is smarter ;-) The
web update installer detects the manipulated system clock and does not allow
to install the update.

Does this help?

Friedrich

[NewsArchive]

Hello Friedrich,

yes, thank you very much this will help.

But i have following problem: how setupbuilder bw. web update installer detects
the manipulated system clock?

Where do you hold the time? On the system, on the app or the internet?

For my app i don´t have to install any on the users system. My app have to run
from only one folder or USB Stick without any registry entries or put files on
the system directories or write to files on the system. THis is for high
security issues.

Thanks an best regards Kai

[NewsArchive]

Hi Kai,

> yes, thank you very much this will help.
>
> But i have following problem: how setupbuilder bw. web update installer
> detects the manipulated system clock?
>
> Where do you hold the time? On the system, on the app or the internet?
>
> For my app i don´t have to install any on the users system. My app have
> to run from only one folder or USB Stick without any registry entries
> or put files on the system directories or write to files on the system.
> THis is for high security issues.

The compilation date is in the installer! Even if a user manipulates the
system clock, the (update) installer knows when a subscription key expires.

There is a built-in "Get Atomic Clock Time..." script function in
SetupBuilder, but the subscription feature does not need this function. Of
course, you can use this atomic clock function to build your own
verification algorithm.

BTW, there is no need to use any registry entry.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

I don't think what the clock says matters at all....

If the users subscription expires 12/31/2007 and the update is dated
1/1/2008, it won't install it.

If you compare the subscription expire date against the updates release
date, you never need to care about the system clock....

paul macfarlane

[NewsArchive]

Hi Paul,

> I don't think what the clock says matters at all....
>
> If the users subscription expires 12/31/2007 and the update is dated
> 1/1/2008, it won't install it.
>
> If you compare the subscription expire date against the updates release
> date, you never need to care about the system clock....

*Absolutely* correct!

Friedrich

[NewsArchive]

OK, thanks much. Now i understand :-)

Very nice.

An other question. I´m using Capesoft Secwin for giving the user access to
different version from my application.

What´s better: installing different Versions from the installer or use secwin
for app rights? I don´t like to much serial numbers:

One for the installer and then for secwin a username, serialno and activation
key? The best i can thinking about was to have only on key. in this key is the
lizenzname, lizenzno for installer an lizenzrights. How i can do this?

Thank again Kai

[NewsArchive]

Kai,

> OK, thanks much. Now i understand :-)
>
> Very nice.

;-)

> An other question. I´m using Capesoft Secwin for giving the user access to
> different version from my application.
>
> What´s better: installing different Versions from the installer or use
> secwin
> for app rights? I don´t like to much serial numbers:
>
> One for the installer and then for secwin a username, serialno and
> activation
> key? The best i can thinking about was to have only on key. in this key is
> the
> lizenzname, lizenzno for installer an lizenzrights. How i can do this?

There is no general answer to this question and it really depends on your
personal preferences.

Installing different versions from the same installer would not be a
problem.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner