Controlling who can run an executable

[Bengt Richter]

On 4 Oct 2005 03:49:50 -0700, "Cigar" <chrisgarland67 at hotmail.com> wrote:

>Paul Rubin wrote:
>> "Cigar" <chrisgarland67 at hotmail.com> writes:
>> > Now that I'm three months into the development of this program, my
>> > client tells me she would like to protect her investment by preventing
>> > her employees from doing the same to her.  (Going to the competition
>> > and using her program.)
>>
>> Exactly what is the threat here?
>
>I think the BIGGEST threat here is a feeling of vulnerablity.  She now
>realizes that she is in a position that her competition was many years
>ago when she came into possesion of program the 'other side' was using
>and that she is now vulnerable.  She wants to feel safe in the
>knowledge that she didn't reach into her pocket and pay thousands of
>dollars for a program that now could now be used by her competition.
>Nobody wants to pay money to level the playing field for all in a
>business environment.
So the biggest threat would seem to be her competition posting requirements
here and having some showoff post a complete solution ;-)

Regards,
Bengt Richter