Bug 1298770 - After upgrading to Fedora 22 a virtual VMware Windows image using the Dokan sshfs client no longer connects to the host
Summary: After upgrading to Fedora 22 a virtual VMware Windows image using the Dokan s...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fuse-sshfs
Version: 22
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-15 01:47 UTC by Paul Lambert
Modified: 2016-07-19 19:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 19:24:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Paul Lambert 2016-01-15 01:47:44 UTC
Description of problem:WMware Windows XP image machine will not share files via sshfs


Version-Release number of selected component (if applicable):
Fedora 22
openssh 6.9p-1
fuse-sshfs 2.5-1

How reproducible:  everytime


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:  The Window Dokan sshfs client has worked with every previous Fedora upgrade.


Additional info:
VMware creates two virtual networks.  I can ping from both sides the actual host IP address as well as the virtual one.

Firewalld ssh is trusted
seLinux is disabled
the SSH config file includes passwords yes
sshd was tested using ssh -l <user name> <local host IP>

Comment 1 Fedora End Of Life 2016-07-19 19:24:04 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.