public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Maglinger, Paul" <PMAGLINGER@scvl.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: FW: File access slow with using key authentication.
Date: Thu, 06 Sep 2012 18:13:00 -0000	[thread overview]
Message-ID: <36DA94300D69184A91500B695547A14833C426FD@COMSTAR1.scvl.com> (raw)
In-Reply-To: <5047CB23.1020306@cygwin.com>

> 
> On 9/5/2012 4:47 PM, Maglinger, Paul wrote:
> > Anyone?
> >
> >
> > Running CYGWIN_NT-6.1-WOW64 1.7.16(0.262/5/3) on Windows 2008R2 box.
> >
> > When using SSH to come in through UNIX, we'd like to use public key
> > authentication. The problem is that when we do it can take up to 5 minutes
> > to even pull down a directory listing on a Windows share using ls -l from
> > the Cygwin terminal. If we do without the key and enter the password
> > manually, things speed up vastly, but we want to authenticate automatically
> > and would prefer to use a key. I believe I understand why it's happening,
> > but I'm having trouble figuring how to work around this. The goal is to have
> > Unix kick off a Perl script residing on the Windows server, which will
> > process files located on a CIFS share on a storage appliance. The Perl
> > script is using UNC to access the shared directories. I've even tried
> > various ways to mount the directories using fstab and that's not helping
> > either. I've only been working with Cygwin for less than a month and would
> > appreciate some insight.
> 
> I've read through your summary above at least twice now but I'm still
> having trouble grokking the details of what you're doing.  Judging by the
> lack of other responses, I'm guessing others are similarly stymied.
> Perhaps you should back up and read the problem reporting guidelines
> found at the link below:
> 
> > Problem reports:       http://cygwin.com/problems.html
> 
> Details are important.  Some pieces of information that may prove useful
> include:
> 
>    1. Does sshing to the same server (presumably running Cygwin's sshd)
>       from that or other Cygwin machine exhibit the same problem?
> 
>    2. How big is the directory you're running 'ls -l' on?  Do the results
>       change if you instead use just '"ls"'?
> 
>    3. Who's the storage appliance's vendor?  Who has permissions to access
>       it?  Keep in mind that public key authentication that's configured
>       for you by default doesn't allow unfettered access to network shares.
>       See <http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview>
>       for a detailed description of the authentication options and
>       restrictions.
> 
> 
> --
> Larry
> 

Thanks for the reply.  I'm new to Cygwin and this list and wasn't sure what details I needed to include.  Let me gather some information and I'll get back with you.

-Paul

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2012-09-06 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 20:25 Maglinger, Paul
2012-09-05 21:36 ` FW: " Maglinger, Paul
2012-09-06  0:04   ` Larry Hall (Cygwin)
2012-09-06 18:13     ` Maglinger, Paul [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=36DA94300D69184A91500B695547A14833C426FD@COMSTAR1.scvl.com \
    --to=pmaglinger@scvl.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).