microsoft / microsoft/terminal

Leverage the Windows Info Protection APIs to unblock enterprise clipboard contents

Open
#10,680 0 comments 1 reaction 0 assignees View on GitHub
Area-UserInterface Issue-Feature Priority-3 Product-Meta
Dominant language
C++
Stars
105k
Forks
9.6k
Avg merge
3d 17h
Merged PRs (30d)
29

Description

We should be able to afford terminal the ability to read clipboard contents as [documented in the Windows Info Protection docs](https://docs.microsoft.com/en-us/previous-versions/windows/desktop/EDP/wip-developer-guide#read-data-from-the-clipboard).

However: we may not want to blindly do so. Terminal should not be able to enter/exit an "enterprise" context, and we have no control over what the application on the receiving end does with the pasted content. We can neither vouch for nor evaluate the veracity of those applications.

Contributor guide

Open the contributing guide

Research direction

Start with the linked Windows Information Protection developer guide, especially its clipboard-reading guidance, and review how Windows Terminal currently handles clipboard access. Done requires an agreed implementation and security policy that addresses enterprise context and the receiving application; the issue does not name an entry point or test.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.