Re: Methods of License Enforcement
From: Dimitri Maziuk (dima_at_127.0.0.1)
Date: 07/15/03
- Next message: Spam Bait: "Re: Methods of License Enforcement"
- Previous message: John Prather: "Re: Command specific SUDO"
- In reply to: Spam Bait: "Methods of License Enforcement"
- Next in thread: Spam Bait: "Re: Methods of License Enforcement"
- Reply: Spam Bait: "Re: Methods of License Enforcement"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 15 Jul 2003 00:53:06 +0000 (UTC)
Spam Bait sez:
> Hi all.
>
> I'm not sure whether this is the most appropriate newsgroup, but anyway...
>
> We've been asked by a client to develop a method of license enforcement
> for some software they've developed and intend to sell. Their software
> is an Access app ( yeah I know ... not particularly secure, but they are
> the customer ) but we intend to build some OCX objects, maybe in Perl,
> and re-use parts of it in later projects in Linux.
Right. Yes. OCX in Perl on Linux. What'll they think of next?
Dima
--
...the mainstream products of major vendors largely ignore these demonstrated
technologies... [Instead, their customers] are left with several ineffective
solutions collected under marketing titles like "defense in depth".
-- Thirty Years Later: Lessons from the Multics Security Evalution
- Next message: Spam Bait: "Re: Methods of License Enforcement"
- Previous message: John Prather: "Re: Command specific SUDO"
- In reply to: Spam Bait: "Methods of License Enforcement"
- Next in thread: Spam Bait: "Re: Methods of License Enforcement"
- Reply: Spam Bait: "Re: Methods of License Enforcement"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|