Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

The bridge serves any same-user process, including input

Abierto
  • ¿Algo no está bien?
#24 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
macos, swift
Área
authorization, desktop-dev, security

Línea de trabajo

The issue concerns the bridge that serves the desktop-client binary over desktop.sock under ~/.local/state/ace-canary/, and the payload names no source files. Start by reproducing the report: run a plain process as the same user and call the socket through the client. Done would mean the runtime verifies the peer's audit token and rejects callers whose parent is not the signed Ace Helper or Ace, which is a design decision still open in the thread.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Found in the githubnext/ace#427 study, on Ace Canary 0.0.46.49–0.0.46.52.

What happens: the bridge authenticates the signed client binary, not the process that runs it. Any process running as the user can execute Ace's client against Ace's socket (~/.local/state/ace-canary/desktop-client and desktop.sock) and get every operation under Ace's Accessibility, Screen Recording and input grants. That includes clicks, inserts, keys, menus and quit.

Shown three ways:

  • A plain node process outside Ace listed apps.
  • Headless Claude Code (Sonnet 5.5) and Codex (gpt-6-astra) drove TextEdit end to end through the MCP server in #12.
  • A channel shell can do the same while that channel's desktop tools are off.

Why it matters:

  • githubnext/ace#379 accepted that shell capture bypasses the off toggle. This extends that to input.
  • Nothing in Ace records that an outside caller acted.
  • macOS shows only Ace as holding the grants.

Options:

  • Same-uid code can't be fully excluded; any secret on disk is readable by it. The bar can still be raised: have the runtime check the peer's audit token, and require that the client's parent is the signed Ace Helper or Ace.
  • A deliberate route for outside agents can then be offered: a standalone signed host app with its own grants, or Ace-hosted MCP that pairs with a channel. See the stretch notes on #12.

At minimum, this belongs in githubnext/ace#427's known gaps and in Ace's desktop tools docs.

Lenguaje dominante
Swift
Estrellas
0
Forks
0
Merge medio
31 min
PR fusionados (30 d)
14

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/desktop-tools

Todos los issues de githubnext/desktop-tools

Issues similares

Más issues de Swift

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.