public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Alviro Iskandar Setiawan <[email protected]>
Cc: GNU/Weeb Mailing List <[email protected]>,
	Hazmi Alfarizqi <[email protected]>,
	Alviro Iskandar Setiawan <[email protected]>
Subject: Re: [PATCH server-a001 v1 1/1] Apply default SSH config and add public keys
Date: Sat, 16 Apr 2022 00:36:40 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAOG64qM=ZAVUmEzkXMckuZiqjCGNDGQT3f0aQXz_TF-Q3UrgtQ@mail.gmail.com>

On 4/16/22 12:29 AM, Alviro Iskandar Setiawan wrote:
> On Sat, Apr 16, 2022 at 12:16 AM Ammar Faizi <[email protected]> wrote:
>>
>> 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.
> 
> The sshd_config in this patch doesn't disable the password auth, tho
> 
> This:
> 
>> +PermitRootLogin prohibit-password
> 
> only disables password auth for root, you're still asked to enter the
> password, but it will never work for root even if the root password is
> correct. However, if the login user is not root, the password auth is
> still valid.
> 
>> +# To disable tunneled clear text passwords, change to no here!
>> +#PasswordAuthentication yes
> 
> This should be set to "no" to really disable password auth.

Ack, yes, my bad. Will fix it in the v2.

-- 
Ammar Faizi

  reply	other threads:[~2022-04-15 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 17:15 [PATCH server-a001 v1 0/1] Apply default SSH config and add public keys Ammar Faizi
2022-04-15 17:15 ` [PATCH server-a001 v1 1/1] " Ammar Faizi
2022-04-15 17:29   ` Alviro Iskandar Setiawan
2022-04-15 17:36     ` Ammar Faizi [this message]
2022-04-15 17:33   ` Alviro Iskandar Setiawan
2022-04-15 17:37     ` Ammar Faizi

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] \
    [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