Ubuntu
openssh package

WSL openssh-server incorrect permissions .ssh

Bug #1890892 reported by Brian Warner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openssh (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Using Ubuntu Windows Subsystem for Linux (WSL)
$ uname -srvmpio
Linux 4.4.0-19041-Microsoft #1-Microsoft Fri Dec 06 14:06:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux

(Prestep required to add port for access to windows firewall)
.ssh directory was set as 777 when 755 (minimum) is required for operation of authentication keys when trying to ssh -i /path-to-key/key user@domain.

Generally poor housekeeping. <3

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: openssh-server 1:7.6p1-4ubuntu0.3
ProcVersionSignature: Microsoft 4.4.0-19041.1-Microsoft 4.4.35
Uname: Linux 4.4.0-19041-Microsoft x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Sat Aug 8 08:44:02 2020
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 127: Error getting authority: Error initializing authority: Could not connect: No such file or directory
SourcePackage: openssh
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Brian Warner (batycoon) wrote :
Revision history for this message
Rafael David Tinoco (rafaeldtinoco) wrote :

Hello Brian,

Thank you for taking the time to file a bug report.

Are you complaining about permissions of ~/.ssh directory ?

I have subscribed Patrick Wu, in charge for WSL1/2 releases but, to be honest, I'm not entirely sure what is the issue you're considering a bug here... could you better describe it ?

Since there is not enough information in your report to begin triage or to differentiate between a local configuration problem and a bug in Ubuntu, I am marking this bug as "Incomplete". We would be grateful if you would: provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community

Changed in openssh (Ubuntu):
status: New → Triaged
Revision history for this message
Hayden Barnes (haydenb) wrote :

I cannot reproduce this issue.

These are the steps I used to attempt to reproduce:

1. Installed Ubuntu 18.04 from the Microsoft Store.
2. Created a new user on launch.
3. Confirmed openssh-server was installed.
4. Confirmed no .ssh folder existed in ~.
5. Ran $ ssh-keygen -t rsa -b 4096 to create keys.
6. Reviewed permissions of the resulting .ssh folder, which are 700, private key 600, and public key 644.

I suspect that something else may have modified the permissions on ~/.ssh.

We do not modify permissions on openssh for WSL anywhere in the image build or Windows unpacking process, it will have the default permissions from the openssh-server package.

Rafael David Tinoco (rafaeldtinoco)
Changed in openssh (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openssh (Ubuntu) because there has been no activity for 60 days.]

Changed in openssh (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.