Bad SSH2 cipher spec
- Vorherrschende Sprache
- Go
- Sterne
- 30.8k
- Forks
- 613
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### Description
Colima appears to be working fine, but Local (https://localwp.com/) cannot push or pull production files and shows this error:
`{"thread":"main","class":"RsyncService","message":"/Users/example/.colima/ssh_config line 13: Bad SSH2 cipher spec '^aes128-gcm@openssh.com,aes256-gcm@openssh.com'.\r\n","level":"warn","timestamp":"2023-08-21T17:32:34.722Z"}
`
So, it looks like there's an error with the Colima SSH config? Due to this error, Local (and possibly other apps) cannot function on a system where Colima is installed.
### Version
Colima Version: 0.5.5
Lima Version: 0.16.0
Qemu Version: 8.0.3
### Operating System
- [ ] macOS Intel <= 12 (Monterrey)
- [X] macOS Intel >= 13 (Ventura)
- [ ] macOS M1 <= 12 (Monterrey)
- [ ] macOS M1 >= 13 (Ventura)
- [ ] Linux
### Output of `colima status`
```
INFO[0000] colima is running using QEMU
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/eriksandall/.colima/default/docker.sock
```
### Reproduction Steps
1. On a computer with both Colima and Local installed, launch Local.
2. Push or pull one of the sites in Local (this process will fail).
3. In the Local error log (local-lightning-verbose.log), you'll find the error referenced above.
### Expected behaviour
_No response_
### Additional context
_No response_
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Bewertung
Dieses Issue wurde noch nicht bewertet.