Re: pcode vs native code
From: Jonathan Wood (jwood_at_softcircuits.com)
Date: 08/21/04
- Next message: Jonathan Wood: "Re: Clearing Memory On Program Exit"
- Previous message: Jonathan Wood: "Re: Registering Controls"
- In reply to: MikeD: "Re: pcode vs native code"
- Next in thread: Ivan Debono: "Re: pcode vs native code"
- Reply: Ivan Debono: "Re: pcode vs native code"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 21 Aug 2004 09:46:49 -0600
Just because there isn't software to convert a VB program back to VB source
code (if there isn't), doesn't mean a hacker can't step through the native
code in a debugger. Unfortunately, I don't know enough about p-code to say
how hard that is to debug.
-- Jonathan Wood SoftCircuits http://www.softcircuits.com Available for consulting: http://www.softcircuits.com/jwood/resume.htm "MikeD" <nobody@nowhere.edu> wrote in message news:OYAMi0yhEHA.2764@TK2MSFTNGP11.phx.gbl... > > "Ivan Debono" <ivanmdeb@hotmail.com> wrote in message > news:ul8R$KyhEHA.3932@TK2MSFTNGP09.phx.gbl... > > Hi all, > > > > Would it be easier for a hacker to crack into a vb6 app compiled in pcode > or > > in native code? > > > Theoretically, p-code should be easier to decompile or hack. But I know of > no decompilers that work with VB6 at all....p-code or native code. > > Mike > > >
- Next message: Jonathan Wood: "Re: Clearing Memory On Program Exit"
- Previous message: Jonathan Wood: "Re: Registering Controls"
- In reply to: MikeD: "Re: pcode vs native code"
- Next in thread: Ivan Debono: "Re: pcode vs native code"
- Reply: Ivan Debono: "Re: pcode vs native code"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|