HDWallet: Use some kind of secure zero instead of memset that could be optimised out

Open
  • Is something wrong?
#34 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c
Domain
cryptography, security

Research direction

Start by locating the HDWallet code that uses memset for sensitive-data cleanup and review the suggested secure-zero construction from the issue context. Check that the replacement is portable to Windows. Done means the sensitive memory is reliably cleared without relying on an optimizable memset implementation.

Written by the indexing model from the issue text.

Description

D - easy X - security-improvement
  • investigate the right construction: potential candidate already suggested
  • make sure it's portable to windows
Dominant language
C
Stars
68
Forks
45
No merged PRs in 30d

Getting set up

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.

More from IntersectMBO/cardano-crypto

All issues in IntersectMBO/cardano-crypto

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.