ChecksumAlgorithm should include SHA384 and SHA512

Open Beginner friendly
#630 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Domain
cryptography

Research direction

Start by locating the ChecksumAlgorithm definition in the debug adapter protocol and review how existing checksum values are declared and documented. Add SHA384 and SHA512 alongside the current algorithms, then verify that the protocol can report both values consistently across DAP.

Written by the indexing model from the issue text.

Description

cl.exe for example supports these as a checksum algorithm: https://learn.microsoft.com/en-us/cpp/build/reference/compiler-options-listed-alphabetically?view=msvc-170, so it would be useful to have these defined in protocol so that these checksums can be easily reported across DAP.

Dominant language
HTML
Stars
1.8k
Forks
173
Avg merge
7d 7h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

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 microsoft/debug-adapter-protocol

All issues in microsoft/debug-adapter-protocol

Similar issues

More Cryptography issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.