Add support to cryptographic PInvoke for ROM<byte> ROS<byte> to reduce allocations

Open
#58 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
security

Research direction

Start with issue #57, then inspect the existing cryptographic P/Invoke implementations and the PAL paths for Win32 and other platforms. Done means supporting ReadOnlyMemory and ReadOnlySpan while reducing the allocations and copying described in this issue.

Written by the indexing model from the issue text.

Description

enhancement up-for-grabs

Is your feature request related to a problem? Please describe.
The existing implementations require a lot of allocating and copying because of historical interfaces in .NET. We can bypass these interfaces and call directly into a PAL (Win32 on Windows, custom on other platforms).

This requires issue #57 to be completed first.

Dominant language
C#
Stars
567
Forks
109
No merged PRs in 30d

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 dotnet/Kerberos.NET

All issues in dotnet/Kerberos.NET

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.