针对tiup部署强制检测SSH RSA加密算法，能否适配其他加密算法
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Feature Request
Is your feature request related to a problem? Please describe:
SSH高版本已经抛弃了RSA方式，但目前tiup部署免密方式还是去检测的RSA，在SSH 禁用了RSA算法后，使用免密方式部署或者扩容tidb集群就会有各种问题。即使使用了--ssh=system 参数，仍去检测了/home/tidb/.ssh
和/home/tidb/.tiup/storage/cluster/clusters/tidb-aaa/ssh/下 有没有id_rsa文件
Describe the feature you'd like:
tiup不应该去关注ssh使用了哪种加密方式，希望tiup后续的版本可以适配SSH多种加密算法，而不是写死一种
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing tiup deployment's SSH key detection, including the --ssh=system entry point and the /home/tidb/.ssh and /home/tidb/.tiup/storage/cluster/clusters/tidb-aaa/ssh/ paths mentioned in the issue. Done means deployment and cluster expansion no longer depend on an id_rsa file and support SSH configurations using other algorithms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100