1. Windows Binding
When I try to bind a windows program, using bindw, I get an .exe file.
When I click on the .exe file from within windows, I get a DOS box pop
up with a messages about "please wait..." or something similar.
After a while, it adds "OK".
You press enter, the DOS box goes away, but the program doesn't run.
Obviously I'm doing something stupid, but I don't know what.
Anyone?
Thanks,
Irv
2. Re: Windows Binding
Hello Irv,
>When I try to bind a windows program, using bindw, I get an .exe file.
>When I click on the .exe file from within windows, I get a DOS box pop
>up with a messages about "please wait..." or something similar.
>After a while, it adds "OK".
>You press enter, the DOS box goes away, but the program doesn't run.
>Obviously I'm doing something stupid, but I don't know what.
>
>Anyone?
>
>Thanks,
>Irv
Heh heh, sounds like that built in security feature Rob told
us about not long ago. If the bind program and the "ex.exe"
file are from different releases it does this (I believe).
It's supposed to keep people from tampering with your bound
executables but I'm not sure how it works.
later,
Lewis Townsend
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
3. Re: Windows Binding
Irv Mullins writes:
> When I try to bind a windows program, using bindw,
> I get an .exe file. When I click on the .exe file from within
> windows, I get a DOS box pop up with a messages
> about "please wait..." or something similar.
>After a while, it adds "OK".
Lewis Townsend writes:
> Heh heh, sounds like that built in security feature Rob
> told us about not long ago. If the bind program and
> the "ex.exe" file are from different releases it does
> this (I believe). It's supposed to keep people from
> tampering with your bound executables but I'm
> not sure how it works.
That's right.
The cryptic message and the delay are supposed to
confuse hackers who might be trying to tamper with
your .exe file. Unfortunately, registered users who
installed 2.1 alpha or beta prior to March 29 of this
year may also see this message if they still have
any old alpha/beta files lying around.
Irv: I'll send you the 2.1 Official Release instructions again,
in case you need them.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
4. Re: Windows Binding
Just out of curiosity, how does that work? Like, if a person were to
change one byte in the person's file, would it get picked up on? How?
When the file is bound, is a value set in the .exe somewhere, of say,
the total sum of all the values of the bytes, or something?
Sorry about all the questions, but I was looking into writing a security
feature like that in C.
Thanks,
Greg Phillips
Robert Craig wrote:
> Irv Mullins writes:
> > When I try to bind a windows program, using bindw,
> > I get an .exe file. When I click on the .exe file from within
> > windows, I get a DOS box pop up with a messages
> > about "please wait..." or something similar.
> >After a while, it adds "OK".
>
> Lewis Townsend writes:
> > Heh heh, sounds like that built in security feature Rob
> > told us about not long ago. If the bind program and
> > the "ex.exe" file are from different releases it does
> > this (I believe). It's supposed to keep people from
> > tampering with your bound executables but I'm
> > not sure how it works.
>
> That's right.
> The cryptic message and the delay are supposed to
> confuse hackers who might be trying to tamper with
> your .exe file. Unfortunately, registered users who
> installed 2.1 alpha or beta prior to March 29 of this
> year may also see this message if they still have
> any old alpha/beta files lying around.
>
> Irv: I'll send you the 2.1 Official Release instructions again,
> in case you need them.
>
> Regards,
> Rob Craig
> Rapid Deployment Software
> http://www.RapidEuphoria.com
--
The Euphoria CD Project:
"Only $9.95, and comes with this juicer absolutely free!"
http://www.redrival.com/euphoria/doslinux.html
5. Re: Windows Binding
- Posted by Robert Craig <rds at ATTCANADA.NET>
Oct 18, 1999
-
Last edited Oct 19, 1999
Greg Phillips writes:
> Just out of curiosity, how does that work? Like, if a person
> were to change one byte in the person's file, would it
> get picked up on? How? When the file is bound, is a value
> set in the .exe somewhere, of say, the total sum of all the
> values of the bytes, or something?
Something like that.
I can't be too specific without reducing security.
Anyway, this is really overkill since a shrouded and scrambled
file will already be extremely hard to tamper with.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
6. Re: Windows Binding
On Mon, 18 Oct 1999 23:40:58 -0400, Robert Craig <rds at ATTCANADA.NET> wrote:
>Greg Phillips writes:
>> Just out of curiosity, how does that work? Like, if a person
>> were to change one byte in the person's file, would it
>> get picked up on? How? When the file is bound, is a value
>> set in the .exe somewhere, of say, the total sum of all the
>> values of the bytes, or something?
>
>Something like that.
>I can't be too specific without reducing security.
>Anyway, this is really overkill since a shrouded and scrambled
>file will already be extremely hard to tamper with.
Would it be possible to change the message that appears when a file has been
tampered with?
-Mark.
7. Re: Windows Binding
- Posted by Greg Phillips <i.shoot at REDNECKS.COM>
Oct 18, 1999
-
Last edited Oct 19, 1999
Hey, I just discovered an additional (intentional?) security feature the "One
moment please...".
I looked at 2.0's bound files, and it appears that the interpreter is included,
then the string 'BIND' is put at the end, followed by the code.
In version 2.1, if you can find the delimiter string (it's probably best I don't
say what it is), you see the shrouded and scrambled source. If you try to add
different code after the string, you end up with the 'One moment please',
whereas if you tried to do the same in 2.0, a proper .exe would be made.
Regards,
Greg Phillips
Liquid-Nitrogen Software wrote:
> On Mon, 18 Oct 1999 23:40:58 -0400, Robert Craig <rds at ATTCANADA.NET> wrote:
>
> >Greg Phillips writes:
> >> Just out of curiosity, how does that work? Like, if a person
> >> were to change one byte in the person's file, would it
> >> get picked up on? How? When the file is bound, is a value
> >> set in the .exe somewhere, of say, the total sum of all the
> >> values of the bytes, or something?
> >
> >Something like that.
> >I can't be too specific without reducing security.
> >Anyway, this is really overkill since a shrouded and scrambled
> >file will already be extremely hard to tamper with.
>
> Would it be possible to change the message that appears when a file has been
> tampered with?
>
> -Mark.