From: Ammar Faizi <[email protected]>
To: GNU/Weeb Mailing List <[email protected]>
Cc: Ammar Faizi <[email protected]>,
Hazmi Alfarizqi <[email protected]>,
Alviro Iskandar Setiawan <[email protected]>
Subject: [PATCH server-a001 v2 0/1] Apply default SSH config and add public keys
Date: Sat, 16 Apr 2022 00:49:39 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
This is v2. Just a single patch here. This does 2 dependent things:
1) Set the default port to 48589, don't use port 22 since we will
inevitably get brute-force SSH attack from random botnets. Even if
it's not really a concern if we're using a private key for the auth,
let's not spam our auth log with many login failed lines.
2) Add maintainers' SSH public keys to the root and main user. Let us
login from the outside world with a key auth.
Please review!
## Changelog
Link v1: https://lore.gnuweeb.org/gwml/[email protected]
v1 -> v2:
- Really disable PasswordAuthentication (comment from Alviro).
- Add Alviro's public key.
Cc: Hazmi Alfarizqi <[email protected]> # @hzmi35
Cc: Alviro Iskandar Setiawan <[email protected]>
Signed-off-by: Ammar Faizi <[email protected]>
---
Ammar Faizi (1):
Apply default SSH config and add public keys
Dockerfile | 16 ++++-
etc/ssh/sshd_config | 123 +++++++++++++++++++++++++++++++++++++++
ssh_keys/authorized_keys | 3 +
3 files changed, 139 insertions(+), 3 deletions(-)
create mode 100644 etc/ssh/sshd_config
create mode 100644 ssh_keys/authorized_keys
--
Ammar Faizi
next reply other threads:[~2022-04-15 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 17:49 Ammar Faizi [this message]
2022-04-15 17:49 ` [PATCH server-a001 v2 1/1] Apply default SSH config and add public keys Ammar Faizi
2022-04-15 17:55 ` [PATCH server-a001 v2 0/1] " Alviro Iskandar Setiawan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox