[futurebasic] Re: [FB] Unalterable Text Resources?

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : November 1999 : Group Archive : Group : All Groups

From: Paul Bruneau <paul_bruneau@...>
Date: Wed, 17 Nov 1999 14:04:02 -0500
Yes and no...

You aren't really creating it "on the fly" at all. You have stored the
41 hex. That is not creating it on the fly. And a 41 hex in a sector (or
text) editor reads as SURPRISE: "A"

So if you want to check your whole string, the whole string will be
right there. If you check every nth character, that can make it harder,
of course.

PB

tedd wrote:
> 
> >> For example, if I was using a STR$ resource, then I would just grab the
> >> resource string and compare it with an internal string
> >
> >This method isn't hard to crack since the string is stored as (at best)
> >ascii that can be easily changed with a sector editor or (at worst)
> >another TEXT resource (!!!) (Depending on your FB prefs)
> >
> >The cracker would just have to change the text twice.
> >
> >jonathan's checksum idea sounds great to me.
> >
> >PB
> 
> PB:
> 
> Yes, I believe that jonathan's checksum idea is the way to go. But, the
> internal string can be created on the fly. For example, in my STR$ routine,
> I take a character, let's say an "A" and then compare that with a 41 HEX --
> the two are equal. You don't need to have a actual internal string to make
> a comparison.
> 
> tedd
> 
> ___________________________________________________________________
> <mailto:tedd@...>                     http://sperling.com/
> 
> --
> To unsubscribe, send ANY message to <futurebasic-unsubscribe@...>