If someone wants it badly enough (say, to run it in a debugger) there’s
not a lot you can do.
We used to do a few things back in the bad old days.
- Break up the password and put it in different fields/variables/array
positions and assemble it at runtime. ( x = a + f + w + otherclass.y
- XOR it with something simple and unwrap when needed.
Combine the two if you care. You can create as many shells of this kind
of silliness as you want, but frankly, it’s faster to break than it is
to hide, so if you only want to hide it from people scanning through a
hex editor or running strings, I wouldn’t do much beyond step 1.
What is the password protecting? Is it an anti-piracy measure or an