On Wednesday 23 March 2016 18:35:22 George N. White III wrote:
Cygwin has become pretty robust, but there are some fundamental
problems
with file permissions/attributes. There is a technical document that goes
into
the gory details, but the basic rule of thumb is that you are safe if you
do all
the work in Cygwin, but problems can arise if your workflow requires mixing
cygwin and Windows apps. Enterprise level environments do tricks with
Windows attributes/permissons that cause grief. In my case, I often got
"access denied" after a file had been touched by Windows apps, and the
Cygwin (POSIX} permissions required by shh for my ~/.ssh directory were
being translated to Windows permissions that then gave "access denied"
in Cygwin's interpretation (e.g., back to POSIX) of the Windows
permissions.
That's thr sort of experience I've had with cygwin in the past. Having said
that, I haven't tried it in a *long* time.
I am still looking for a solution to provide me with a working sftp server
which is really the only bit I need from SSH (*) but for now I'm making do
with sharing the folder from the Win7 box and mounting it using a fstab entry
on the server.
(*) it would be nice to have ssh access to the server so that I could
integrate/automate other tasks using Perl and Net::SSH