Re: Unwanted PRIVATE symbols in masm obj file
- From: "rhyde@xxxxxxxxxx" <spamtrap@xxxxxxxxxx>
- Date: 2 Apr 2007 06:55:18 -0700
On Mar 29, 1:11 pm, spamt...@xxxxxxxxxx wrote:
Hi Robert,
This was sort of a security issue.
I needed to send an OBJ file to someone, but didn't want
him to see the names of ALL procedures, only the public ones.
The solution I came up with is:
first, assemble the file to OMF format, then give it to this BAT file:
lib %1.obj
lib /EXTRACT:%1.obj %1.lib
del %1.lib
This is, basically, OMF2COFF with the tools I have handy.
Actually, MSLINK will automatically convert OMF files to COFF files
during the linking process, so you shouldn't need to do even this
(assuming you're using a reasonably recent version of the linker).
Do keep in mind, however, that if you're distributing .obj files,
security is almost a non-issue as they are *very* easy to disassemble.
If the particular name of the function is an issue, just use
conditional assembly in your source file to change the name for actual
release (e.g., use a textequ inside conditional assembly to change the
name of the procedure everywhere it appears in the program).
Cheers,
Randy Hyde
.
- Prev by Date: Re: calling convention - increase stack before call
- Next by Date: Re: calling convention - increase stack before call
- Previous by thread: Re: newbie question about dword ptr
- Next by thread: what does the first MB of memory look like, directly after bootstrapping
- Index(es):
Relevant Pages
|
