Re: Controlling who can run an executable

2005-10-07 Thread Magnus Lycka
Cigar wrote: > What I want: > - the simplest thing that could possibly work! A splash screen that informs the user that it's confidential data, and that unauthorized use will lead to prosecution? Besides, I think it's not the program you need to protect, but the data. Think about that. Who cares

Re: Controlling who can run an executable

2005-10-04 Thread Cigar
Tony Nelson wrote: > In article <[EMAIL PROTECTED]>, > "Cigar" <[EMAIL PROTECTED]> wrote: > > > I am developing a program for a client. She runs a shop where her > > clients bring in items for sale or short term buyback. Development of > > the program has been going great but she's mentioned th

Re: Controlling who can run an executable

2005-10-04 Thread Cigar
Istvan Albert wrote: > > I could ask her, "If you can't break it is that good enough security?" > > Guess not. Most non-programmers think everyone else who knows some > programming is a some sort of hacker genius. > > Instead come up with a simple solution then explain her how it will > works. I t

Re: Controlling who can run an executable

2005-10-04 Thread Istvan Albert
> I could ask her, "If you can't break it is that good enough security?" Guess not. Most non-programmers think everyone else who knows some programming is a some sort of hacker genius. Instead come up with a simple solution then explain her how it will works. I think in the ensuing conversation y

Re: Controlling who can run an executable

2005-10-04 Thread Cigar
Istvan Albert wrote: > >was using to track clients and transactions. He couldn't demonstrate > >the program for one reason or another because it was protected in a way > >that neither could circumvent. (She didn't remember how it was > >protected, she had hired this person a long time ago.) > > I

Re: Controlling who can run an executable

2005-10-04 Thread Cigar
Myles Strous wrote: > What's more, Tim Golden's wmi module (see > http://tgolden.sc.sabren.com/python/wmi.html) makes getting at these > numbers very easy: > > import wmi > c = wmi.WMI () > for thingy in c.Win32_NetworkAdapter(): > print "Network Adaptor", thingy.MACAddress > for thingy in c.Win

Re: Controlling who can run an executable

2005-10-04 Thread x_tek
I would write a companion program that works like this: $ protector -lock filename.exe and $ protector -unlock filename.exe the -lock switch would simply get the file size of filename.exe then generate a random chunk of data the same size, xor it with filename.exe and write the chunk data to a

Re: Controlling who can run an executable

2005-10-04 Thread Bengt Richter
On 4 Oct 2005 03:49:50 -0700, "Cigar" <[EMAIL PROTECTED]> wrote: >Paul Rubin wrote: >> "Cigar" <[EMAIL PROTECTED]> 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 doi

Re: Controlling who can run an executable

2005-10-04 Thread Cigar
Paul Rubin wrote: > Suppose that competitor's program that her employee had illicitly > brought her wasn't protected, so she was able to run it. You might > ask her whether, ethical issues aside, she would be willing to use it > on a daily basis, given it sounds like people in her industry know >

Re: Controlling who can run an executable

2005-10-04 Thread Tony Nelson
In article <[EMAIL PROTECTED]>, "Cigar" <[EMAIL PROTECTED]> wrote: > I am developing a program for a client. She runs a shop where her > clients bring in items for sale or short term buyback. Development of > the program has been going great but she's mentioned that there is a > 'feature' comin

Re: Controlling who can run an executable

2005-10-04 Thread Istvan Albert
>was using to track clients and transactions. He couldn't demonstrate >the program for one reason or another because it was protected in a way >that neither could circumvent. (She didn't remember how it was >protected, she had hired this person a long time ago.) I'd venture to guess that neither

Re: Controlling who can run an executable

2005-10-04 Thread Michael Ekstrand
On Tuesday 04 October 2005 01:43, Svennglenn wrote: > Have the program check for a file hidden somewhere on the computer. > For instance, if the file dummyfile.dll doesn't exist in the > windows/system32 folder the program just doesn't start. And when you > install the program on her computer just

Re: Controlling who can run an executable

2005-10-04 Thread Paul Rubin
"Cigar" <[EMAIL PROTECTED]> writes: > 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

Re: Controlling who can run an executable

2005-10-04 Thread Cigar
Paul Rubin wrote: > "Cigar" <[EMAIL PROTECTED]> 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 progra

Re: Controlling who can run an executable

2005-10-04 Thread Paul Rubin
"Cigar" <[EMAIL PROTECTED]> writes: > I may have to just put password protection in and if she hangs herself > by 'sharing' the password with underlings she trusts (at the > present)... again that's outside of my control of protecting her. You could have the password automatically change once a mo

Re: Controlling who can run an executable

2005-10-04 Thread Cigar
Mike Meyer wrote: > First thing to know; you can't stop someone who's sufficiently > determined to run the program. I have explained to her that I can't prevent someone who REALLY wants her program from tossing a rock through her front window and making off with her PC. They'd get the hardware an

Re: Controlling who can run an executable

2005-10-03 Thread Svennglenn
> What I want: > - the simplest thing that could possibly work! > Have the program check for a file hidden somewhere on the computer. For instance, if the file dummyfile.dll doesn't exist in the windows/system32 folder the program just doesn't start. And when you install the program on her compute

Re: Controlling who can run an executable

2005-10-03 Thread Myles Strous
Mike Meyer wrote: > You don't need to install special hardware to get that. There are a > number of pieces of hardware that you can find in a modern computer > that may have a unique serial number you can use as a > dongle. Possibilities include a CPU serial number, an HD serial > number, and the

Re: Controlling who can run an executable

2005-10-03 Thread Paul Rubin
"Cigar" <[EMAIL PROTECTED]> 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 thr

Re: Controlling who can run an executable

2005-10-03 Thread Mike Meyer
"Cigar" <[EMAIL PROTECTED]> 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.) First thing to know; yo

Controlling who can run an executable

2005-10-03 Thread Cigar
I am developing a program for a client. She runs a shop where her clients bring in items for sale or short term buyback. Development of the program has been going great but she's mentioned that there is a 'feature' coming up in the next couple of weeks that she'd like me to implement that has me