Eric Traut 09bc28f348 Restrict Windows IDE pipe client impersonation (#39020) ...

## Why

Windows named pipe servers can impersonate connected clients. IDE context
connections only require the server to identify the client, so they should not
grant broader impersonation rights.

## What changed

Open Windows IDE context pipes with `SECURITY_SQOS_PRESENT` and
`SECURITY_IDENTIFICATION`, limiting the server's impersonation token to the
identification level.

## Testing

Add a Windows regression test that connects to a named pipe, asks the server to
impersonate the client, and verifies that the resulting token has the
`SecurityIdentification` level.

GitOrigin-RevId: 51ef080f3367857987e03b0113a476040ea40e56

2026-08-17 16:34:21 +00:00

..

ipc.rs

Prefer the Codex home socket for Unix IDE context (#32302)

2026-07-11 01:15:48 +00:00

prompt.rs

…

windows_pipe_tests.rs

Restrict Windows IDE pipe client impersonation (#39020)

2026-08-17 16:34:21 +00:00

windows_pipe.rs

Restrict Windows IDE pipe client impersonation (#39020)

2026-08-17 16:34:21 +00:00