aws / aws/amazon-q-developer-cli
kiro-cli can't read sshd_config
- Lingua principale
- Rust
- Stelle
- 2k
- Fork
- 439
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
### Checks
- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again
### Operating system
Linux 5.10.247-246.989.amzn2int.x86_64 - Amazon Linux 2
### Expected behaviour
Checking my kiro-cli install with kiro-cli doctor, I expected no errors since my /etc/ssh/sshd_config file contains the suggested two lines:
AcceptEnv Q_SET_PARENT
AllowStreamLocalForwarding yes
I have also run sudo systemctl restart sshd, disconnected, and reconnected multiple times.
### Actual behaviour
Stuck in this loop:
dev-dsk-dhughead-1e-f67adea6 % kiro-cli doctor
✘ sshd config: Could not read sshd_config
The /etc/ssh/sshd_config file needs to have the following line:
AcceptEnv Q_SET_PARENT
AllowStreamLocalForwarding yes
If your sshd_config is already configured correctly then:
1. Restart sshd, if using systemd: sudo systemctl restart sshd
2. Disconnect from the remote host
3. Run kiro-cli integrations install ssh on the local machine
4. Reconnect to the remote host and run kiro-cli doctor again
✘ Doctor found errors. Please fix them and try again.
If you are not sure how to fix it, please open an issue with kiro-cli issue to let us know!
### Steps to reproduce
_No response_
### Environment
```yaml
[q-details]
version = "1.23.1"
hash = "faddc2c7ee17078025a62a8dfad6543a4154d2fa"
date = "2025-12-23T23:03:02.919205Z (20d ago)"
variant = "minimal"
[system-info]
chip = "Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz"
total-cores = 8
memory = "61.36 GB"
[system-info.os.linux]
kernel_version = "5.10.247-246.989.amzn2int.x86_64"
id = "amzn"
name = "Amazon Linux"
pretty_name = "Amazon Linux 2"
version_id = "2"
version = "2"
variant = "internal"
[environment]
cwd = "/local/home/USER"
cli-path = "/local/home/USER"
os = "Linux"
shell-path = "/local/home/USER/.toolbox/tools/toolbox/1.1.2513.0/toolbox-exec"
shell-version = "5.8"
install-method = "toolbox"
in-ssh = true
[env-vars]
PATH = "/home/USER/.rbenv/bin:/home/USER/.rbenv/bin:/home/USER/.rbenv/shims:/home/USER/.rbenv/bin:/home/USER/.toolbox/bin:/usr/local/bin:/usr/bin:/home/USER/bin:/usr/local/sbin:/usr/sbin:/home/USER/.local/bin"
Q_SET_PARENT_CHECK = "1"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia con `kiro-cli doctor` nella sessione SSH Amazon Linux 2 segnalata e confronta la sua gestione di `/etc/ssh/sshd_config` con le due righe richieste. Il lavoro è completato quando il controllo di doctor accetta il file configurato dopo i passaggi documentati di riavvio di sshd, disconnessione, riconnessione e installazione dell’integrazione SSH.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- linux, rust
- Ambito
- cli, networking, operating-systems
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 45/100