You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PubkeyAuthentication is actually hardcoded as true.
We have some cases in our cluster were we want to set it to false globally, but true for some Matched Addresses only (using Match Address directive) like the following configuration example:
# /etc/ssh/sshd_config
...
PubkeyAuthentication no
...
Match Address 192.168.1.0/24
PubkeyAuthentication yes
...
Solution
Add a new variable ssh_pubkey_authentication and set it true by default.
As like, we can override this global default value to false and set our specific Match Address rules.
Please check the following PR: #749
Alternatives
No response
Additional information
...
The text was updated successfully, but these errors were encountered:
Description
PubkeyAuthentication
is actually hardcoded astrue
.We have some cases in our cluster were we want to set it to false globally, but true for some Matched Addresses only (using Match Address directive) like the following configuration example:
Solution
Add a new variable
ssh_pubkey_authentication
and set ittrue
by default.As like, we can override this global default value to
false
and set our specificMatch Address
rules.Please check the following PR: #749
Alternatives
No response
Additional information
...
The text was updated successfully, but these errors were encountered: