Boshi Lian
Boshi Lian
i assume you are running ``` ssh user@xxx -i key ``` could you please confirm if key.pub in `/home/user/sshpiper/keys/authorized_c1` sshpiper will treat user as not matched if key.pub not found...
got it, could you please test if last know stable [v1.2.8](https://github.com/tg123/sshpiper/releases/tag/v1.2.8) good for your case also i am working on a fix to it
will support multiple key `--no-check-perm`: you need to set yaml to 400 (chmod 400 xxx.yaml) `ignore-hostkey: true`: to have secure connection, need to put upstream hostkey.pub to `known_hosts_data`
ah 600 is good too see code here https://github.com/tg123/sshpiper/blob/38be0fdd814aa22486c3197fbba8577dfb3be3a9/plugin/yaml/yaml.go#L78
the `known_hosts_data` here is for sshpiper to verify upstream (real sshd) if `ignore-hostkey: true` works, then you are putting wrong key
hi @ApocalypseCalculator i added testcase cover your scenario in #396 seems ssh client worked well (current sshpiper master [6fe67e3](https://github.com/tg123/sshpiper/commit/6fe67e3f5c4ea39ec2f4fb1d13ba11bbb19cf378), with ssh client OpenSSH_9.2p1 Debian-2+deb12u2, OpenSSL 3.0.11 19 Sep 2023) could...
please rebase with current master to get pr green
you can try `slngen` directly let me think how to make it better, should be `dotnet msbuild /Restore /t:SlnGen kubernetes-client.proj`
/LGTM
good catch, would you like to send the pr