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

megathread: Known sudo issues in Windows insider builds

Abierto
  • ¿Algo no está bien?
#4 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
15/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
rust
Área
operating-systems

Línea de trabajo

Comienza leyendo las listas de tareas de la issue #4 y las notas de release/build referenciadas. No se nombran archivos fuente ni pruebas, y cada bug listado está marcado como corregido, por lo que la issue no define un cambio accionable ni una condición clara de finalización para un nuevo colaborador.

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

Descripción

Issue-Bug Issue-Scenario

This is a megathread for all the issues that we had previously identified before sudo was made public. There's about a 3-week delay between us fixing issues, and the fixes being available to Insiders. This creates a bit of a backlog of issues that we've already fixed, but that are still present in the Insider builds.

### Bugs fixed by 1.0.0-38, !10359415
- [x] Sudo server listens for a single connection
- [x] `sudo -N` always starts Windows applications in C:\windows\system32 - this is by design, but mitigated with:
- [x] #22 
- [x] Sudo events weren't showing up in Event Viewer
- [x] Regression from `26068`: `sudo pwsh` reports an error about "Processing -File '' failed: The path is empty"
- [x] Sudo with an explicit mode will report an error instead of clamping to the available mode

In ge_release_we_adept_dev on 2/28. ETA ~3/20?

### Bugs fixed by 1.0.0
- [x] `sudo` seemingly doesn't return the exit code of the target application??
- [x] Localization is quite a bit better
- [x] Sudo does a _better_ job of checking that the client process is sudo
- [x] The elevated sudo exits immediately after launching the target process
- [x] #21 
- [x] `--newWindow` was replaced with `--new-window` (!10282477)
- [x] Added `-N` for `--new-window` (!10282477)
- [x] `--disableInput` was replaced with `--disable-input` (!10282477)

Apparently this one is in ge_release 26068, 2/25

### Bugs fixed by 0.1.6
- [x] Localization is largely not available
- [x] Sudo doesn't log requests to the Event Viewer
- [x] `sudo dir` from powershell will do the `cmd` `dir`, not the powershell `dir`
- [x] `sudo -E --newWindow cmd` doesn't actually pass env vars to the target process
- [x] eleveated sudo doesn't check that the client process is sudo (MSFT:48520593, fixed in !10167063)

0.1.6 merged to OS.2020 in !10239101. It's in ge_release_we_adept as of 2/14, and ge_release as of 2/25, build 26068

### Bugs fixed by 0.1.5 (Windows Insiders build 26052)
- [x] The sudo icon is out of date
- [x] MSFT:48453238 Piping to files is broken
Lenguaje dominante
Rust
Estrellas
5.9k
Forks
180
Sin PR fusionados en 30 d

Preparar el entorno

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 microsoft/sudo

Todos los issues de microsoft/sudo

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.