m4b / m4b/goblin

IMAGE_DIRECTORY_ENTRY_COM_DESCRIPTOR

Open
#315 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1.5k
Forks
202
PR merge metrics
No merged PRs in 30d

Description

Thanks for this great crate. Using it in a forensic file tool here: https://github.com/theflakes/fmd

I'm trying to figure out how to query the optional_header for this: IMAGE_DIRECTORY_ENTRY_COM_DESCRIPTOR

Trying to identify .Net bins and then hash the TypeDef information.

thanks again,
Brian

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the PE optional_header handling and locating how IMAGE_DIRECTORY_ENTRY_COM_DESCRIPTOR is represented or exposed. Confirm the expected way to query this directory for .NET binaries, then define completion as making that information available for identifying such binaries and inspecting their TypeDef data.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
reverse-engineering
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.