actions/ssh-key-action
1
0
Fork 0
mirror of https://github.com/shimataro/ssh-key-action.git synced 2025-06-19 22:52:10 +10:00
Code Activity

* target -> server

Browse source
This commit is contained in:
shimataro 2020-01-26 16:04:18 +09:00
parent 5cc8e1d510
commit 73c06f97bd
No known key found for this signature in database
GPG key ID: BE92C05736911A9D
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
README.md
View file

@ -93,16 +93,16 @@ Check belows:
I recommend **rsync via bastion**. I recommend **rsync via bastion**.
It has some advantages over other methods: It has some advantages over other methods:
* You only need to use this action **only once** even if it is necessary to transfer to multiple targets. * You only need to use this action **only once** even if it is necessary to transfer to multiple servers.
* Other methods require to use it multiple times in order to connect to each targets. * Other methods require to use it multiple times in order to connect to each servers.
* Of course, it is necessary to install bastion public key on targets, and host keys on bastion. But you don't have to update workflow files and `secrets` even if number of targets changed. * Of course, it is necessary to install bastion public key on servers, and server keys on bastion. But you don't have to update workflow files and `secrets` even if number of servers changed.
* `rsync`: * `rsync`:
* is faster than others. * is faster than others.
* will **NOT** break files even if disconnected during sending. * will **NOT** break files even if disconnected during sending.
* can remove files that don't exist in target. * can remove files that don't exist in server.
* SCP is [deprecated by OpenSSH](https://www.openssh.com/txt/release-8.0) due to outdated and inflexible protocol. * SCP is [deprecated by OpenSSH](https://www.openssh.com/txt/release-8.0) due to outdated and inflexible protocol.
* Using bastion is more secure because: * Using bastion is more secure because:
* it is not necessarily to expose SSH port on target servers to public. * it is not necessarily to expose SSH port on server servers to public.
* it requires to shutdown only bastion when security incident ―e.g., private key leaked, GitHub jacked― occurs. * it requires to shutdown only bastion when security incident ―e.g., private key leaked, GitHub jacked― occurs.
## License ## License