- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Utility to change "image file identification"?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2012 10:58 AM
07-19-2012 10:58 AM
Re: Utility to change "image file identification"?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2012 12:08 AM
07-20-2012 12:08 AM
Re: Utility to change "image file identification"?
>>> Find me a single non corrupted .EXE...
It took some time, because I usually don't have access to an Integrity. I let the linker create one for you:
Number Type Name File Address
File Size Flags
...
7. NOTE .note 0000000000001200
0000000000000218 ------------------------------
I didn't use readef, but I'm sure you will see that the size of the note section is 0x218. As I said, it is possible. And if it is possible, it will show up, sooner or later. That's my experience.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2012 06:14 AM
07-21-2012 06:14 AM
Re: Utility to change "image file identification"?
Bob,
Refer to the NT_VMS_ORIG_DYN .notes subsection of the readelf output I posted. Although the Image identification is changed, the ORIG_DYN .note subsection still shows V1.0. I haven't checked thoroughly but I do not seem to recollect that analyze/image displays such information.
I strongly agree with you : this kind of practice makes software support slightly more complicated and should be best effort avoided. However, when developers do not follow strict Linker's IDENTIFICATION option setting, the code I propose is a mean to address such lack. If I refer to David Lennon original post and need, this addresses the problem he is faced with.
Yours sincerely,
Philippe Vouters (ex-HP French support)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2012 04:04 PM
07-25-2012 04:04 PM
Re: Utility to change "image file identification"?
>In an .EXE, there is an upperbound for .note section size.
>For .OBJ files, the .note sections can theoretically (there's that word again) be much larger than 512.
Gee, you are thinking too small. ;-)
For HP-UX using the aC++ compiler, the compiler ecom itself has, the HP-UX linker just concatenates the .notes:
41 NOTE 0000000000000000 00000000048d5ba8 000fb590 .note
1,029,520 bytes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2012 06:55 PM
07-29-2012 06:55 PM
Re: Utility to change "image file identification"?
Currently, none of the .note entries in object files are carried over to the executable. Such things have been suggested in the past for people asking "what source files or compiler versions were used to create my executable". The answer has always been "you should have saved the linker .MAP file, it tells you almost all of that". If that would ever changes, then yes, the executable's .note section would be much larger. It would take up more disk space, but not make the activation that much slower as the .notes would still be in an ELF section, not an ELF segment.
- « Previous
- Next »