m4b / m4b/goblin

write support for PE / Signing PE for UEFI

Open
#357 2 comments 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

As part of signing PE objects for booting UEFI payloads with secureboot, we (@RaitoBezarius and I) would need to add a PKCS#7 signature to PE objects.

This comes along with the efforts @RaitoBezarius already submitted in #354 and the request for authenticode support in #355.

@m4b I'd love for your opinion on that, and input on where to direct efforts.
Should we target https://github.com/m4b/faerie for write support, or should put PE write support in goblin?

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

No files, tests, or entry points are named. Start by reviewing issues #354 and #355 and the existing PE support in goblin, then compare the proposed write support with faerie. Done requires a maintainer decision on the target project and a defined approach for adding PKCS#7 signatures to PE objects for UEFI secure boot.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
reverse-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.