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
Windows don't have a system-wide ssh folder ($env:Programdata\ssh) by default.
Assume a non-admin user creates the system-wide ssh folder and then the admin user installs the win32-OpenSSH.
Admin user later manually creates the system-wide ssh_config ($env:Programdata\ssh\ssh_config). By default, this file inherits the parent folder permissions i.e., the non-admin user has the write permission.
This is not desirable.
Proposed fix - ssh.exe should check the file permissions on system-wide ssh_config file. If this file has write permissions for non admin users then fail the ssh connection.
The text was updated successfully, but these errors were encountered:
OpenBSD team plan to fix this in next version i.e., OpenSSH v8.6
bagajjal
changed the title
Check file permissions of system wide ssh_config file.
[Security]Check file permissions of system wide ssh_config file.
May 14, 2021
Windows don't have a system-wide ssh folder ($env:Programdata\ssh) by default.
Assume a non-admin user creates the system-wide ssh folder and then the admin user installs the win32-OpenSSH.
Admin user later manually creates the system-wide ssh_config ($env:Programdata\ssh\ssh_config). By default, this file inherits the parent folder permissions i.e., the non-admin user has the write permission.
This is not desirable.
Proposed fix - ssh.exe should check the file permissions on system-wide ssh_config file. If this file has write permissions for non admin users then fail the ssh connection.
The text was updated successfully, but these errors were encountered: