Home All Groups Group Topic Archive Search About

Hide an exadecimal number within an executable file

Author
15 Nov 2006 8:43 AM
Nicola Taibi
Hi,
In a visual basic .net 2003 application I use an hexadecimal number to
encrypt a file as a symmetric key.
Is it possible to detect, within the executable, the number above to
consequently decrypt the same file?
How secure is to hide an hexadecimal number to be used as password or key
inside an executable file?
String are easy to find.

Any help is appreciated,
Nicola Taibi
whisky1***@yahoo.it
www.geocities.com/whisky1767

Author
15 Nov 2006 2:38 PM
Herfried K. Wagner [MVP]
"Nicola Taibi" <nta***@libero.it> schrieb:
> In a visual basic .net 2003 application I use an hexadecimal number to
> encrypt a file as a symmetric key.
> Is it possible to detect, within the executable, the number above to
> consequently decrypt the same file?

Yes, using ILDASM or Reflector, for example.  You may let the user enter the
key or store it on a smartcard.

--
M S   Herfried K. Wagner
M V P  <URL:http://dotnet.mvps.org/>
V B   <URL:http://dotnet.mvps.org/dotnet/faqs/>
Author
15 Nov 2006 3:02 PM
rowe_newsgroups
Couldn't you program the encryption routine in vb6 (or another language
that couldn't be easily disassembled) and call that from the .Net
program? Also would the Dotfuscator tool help here?

I haven't tried either approach so I'm not sure if they will work or
not - hopefully one of the gurus will shed some light...

Thanks,

Seth Rowe


Herfried K. Wagner [MVP] wrote:
Show quoteHide quote
> "Nicola Taibi" <nta***@libero.it> schrieb:
> > In a visual basic .net 2003 application I use an hexadecimal number to
> > encrypt a file as a symmetric key.
> > Is it possible to detect, within the executable, the number above to
> > consequently decrypt the same file?
>
> Yes, using ILDASM or Reflector, for example.  You may let the user enter the
> key or store it on a smartcard.
>
> --
>  M S   Herfried K. Wagner
> M V P  <URL:http://dotnet.mvps.org/>
>  V B   <URL:http://dotnet.mvps.org/dotnet/faqs/>