From 1d406e8c577370aa0a8351123ba092340595d889 Mon Sep 17 00:00:00 2001 From: shimataro Date: Sun, 26 Jan 2020 16:51:33 +0900 Subject: [PATCH] * fix some sendences --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 049278a..5ae7112 100644 --- a/README.md +++ b/README.md @@ -76,7 +76,7 @@ steps: ## FAQ -### SSH failed even though installed key. +### SSH failed even though key has been installed. Check belows: @@ -88,7 +88,7 @@ Check belows: * The former is **HIGHLY** recommended for security reason. * I'm planning to make `known-hosts` required in v2. -### How do I use encrypted SSH key by passphrase? +### How do I use encrypted SSH key? This action doesn't support encrypted key directly. Here are some methods: @@ -98,7 +98,7 @@ Here are some methods: * `expect` command: please be careful not to expose passphrase to console * `SSH_ASKPASS` environment variable: it may be troublesome -### Which one is the best way for transferring files, "SCP", "SCP via bastion", "SFTP", "SFTP via bastion", "rsync" or "rsync via bastion"? +### Which one is the best way for transferring files, "direct SCP", "SCP via bastion", "direct SFTP", "SFTP via bastion", "direct rsync" or "rsync via bastion"? I recommend **rsync via bastion**. It has some advantages over other methods: @@ -112,7 +112,7 @@ It has some advantages over other methods: * 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: - * it is not necessarily to expose SSH port on server servers to public. + * it is not necessarily to expose SSH port on servers to public. * it requires to shutdown only bastion when security incident ―e.g., private key leaked, GitHub jacked― occurs. ## License