Zeroise on drop for types containing private key material

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
cryptography, security

Research direction

Start with pull request 79, which contains the referenced discussion, and inspect the types containing private key material there. Done means the affected types zeroize on drop without introducing the breaking change described in this issue.

Written by the indexing model from the issue text.

Description

next-major-release

As discussed in https://github.com/rustls/pki-types/pull/79 adding Drop to any type is a breaking change.

Dominant language
Rust
Stars
42
Forks
55
Avg merge
3d 7h
Merged PRs (30d)
4

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 rustls/pki-types

All issues in rustls/pki-types

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.