Update Mutex usage in .NET 9 when the "user-specific named mutex" feature is added

Open
#3,797 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
security

Research direction

No files, tests, or entry points are identified in the issue. Find the current Mutex usage in PSReadLine, then review the .NET 9 user-specific named mutex feature and determine how availability should be handled. Done means the implementation uses that feature when available and preserves the intended mutex behavior without the reported security concern.

Written by the indexing model from the issue text.

Description

Issue-Enhancement
Prerequisites
  • Write a descriptive title.
Description of the new feature/enhancement

When using Mutex in .NET Core, .NET creates a folder in the temp directory with world write access, which raises potential security concerns. .NET 9 will add a new feature to offer user-specific named mutex, and we will need to switch to that when it's available.

Proposed technical implementation details (optional)

No response

Dominant language
C#
Stars
4.4k
Forks
341
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 PowerShell/PSReadLine

All issues in PowerShell/PSReadLine

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.