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

* fix sentences

Browse source
This commit is contained in:
shimataro 2020-01-26 19:53:43 +09:00
parent b6835ff49c
commit 6c1366e61a
No known key found for this signature in database
GPG key ID: BE92C05736911A9D
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -91,12 +91,12 @@ Check belows:
### How do I use encrypted SSH key?
This action doesn't support encrypted key directly.
Here are some methods:
Here are some solutions:
* decrypting key beforehand: best bet, and works on any VM
* `sshpass` command: next best bet, but not supported on Windows
* `expect` command: please be careful not to expose passphrase to console
* `SSH_ASKPASS` environment variable: it may be troublesome
* `expect` command: be careful not to expose passphrase to console
* `SSH_ASKPASS` environment variable: might be troublesome
### Which one is the best way for transferring files, "direct SCP/SFTP/rsync" or "SCP/SFTP/rsync via bastion"?
@ -108,7 +108,7 @@ It has some advantages over other methods:
* 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`:
* is faster than others.
* will **NOT** break files even if disconnected during transferring.
* does **NOT** break files even if disconnected during transferring.
* 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.
* Using bastion is more secure because: