Alfred von Campe wrote:
A quick update on the my situation (I am the original poster). After
removing Cygwin and reinstalling it, re-running ssh-host-config, and
making the home directory in /etc/passwd a local directory (i.e., not a
network drive), I am now able to log into the Windows system
A quick update on the my situation (I am the original poster). After
removing Cygwin and reinstalling it, re-running ssh-host-config, and
making the home directory in /etc/passwd a local directory (i.e., not
a network drive), I am now able to log into the Windows system from a
Linux system
On Feb 7 17:51, Dave Korn wrote:
> On 07 February 2008 16:16, Corinna Vinschen wrote:
> > It's not about speed, it's about problems with Samba remote shares.
>
> Oh, thanks for the correction :)
>
> > smbntsec doesn't work well with Samba if you don't run an integrated
> > domain environment w
On 07 February 2008 16:16, Corinna Vinschen wrote:
> On Feb 7 14:46, Dave Korn wrote:
>> On 06 February 2008 15:48, Alfred von Campe wrote:
>>> On Feb 6, 2008, at 9:55, Dave Korn wrote:
>>>
How do the perms on /home/av16209/.ssh/* look? How do they look with
CYGWIN=smbntsec?
>>>
>>
On Feb 7 14:46, Dave Korn wrote:
> On 06 February 2008 15:48, Alfred von Campe wrote:
> > On Feb 6, 2008, at 9:55, Dave Korn wrote:
> >
> >> How do the perms on /home/av16209/.ssh/* look? How do they look with
> >> CYGWIN=smbntsec?
> >
> > Interesting. I had CYGWIN set to "binmode tty ntsec"
On Feb 7, 2008, at 9:46, Dave Korn wrote:
It all depends where you keep your home directory. For a home on
your local
HD, that's fine, but if you have home on a network share, you need
'smbntsec',
since ntsec defaults to only cover local drives for speed.
Yes, our home directories are o
On 06 February 2008 15:48, Alfred von Campe wrote:
> On Feb 6, 2008, at 9:55, Dave Korn wrote:
>
>> How do the perms on /home/av16209/.ssh/* look? How do they look with
>> CYGWIN=smbntsec?
>
> Interesting. I had CYGWIN set to "binmode tty ntsec" according to
> some instructions I found by go
If you want this enabled indelibly just for the sshd service and
you don't
want to go skulking around in the registry, you can re-run ssh-host-
config
and specify 'smbntsec' as one of the settings when it asks you what
you want
for the service. This is a good thing to do because it allows you
Alfred von Campe wrote:
On Feb 6, 2008, at 9:55, Dave Korn wrote:
How do the perms on /home/av16209/.ssh/* look? How do they look with
CYGWIN=smbntsec?
Interesting. I had CYGWIN set to "binmode tty ntsec" according to some
instructions I found by googling. Here are the relevant results:
On Feb 6, 2008, at 9:55, Dave Korn wrote:
How do the perms on /home/av16209/.ssh/* look? How do they look
with
CYGWIN=smbntsec?
Interesting. I had CYGWIN set to "binmode tty ntsec" according to
some instructions I found by googling. Here are the relevant results:
bash-3.2$ CYGWIN=
I have had similar thing happen to me before. Please try stop and
start the CYGWIN sshd service in Windows, try again. If that works,
then we might be having the same problem.
I forgot what I did exactly. Looking at my current setup, it seems
that the "TCP/IP Protocol Driver" is added in sshd's de
On 06 February 2008 14:41, Alfred von Campe wrote:
> debug1: Host 'gandalf' is known and matches the RSA host key.
> debug1: Found key in /home/av16209/.ssh/known_hosts:101
> debug1: ssh_rsa_verify: signature correct
> debug1: SSH2_MSG_NEWKEYS sent
> debug1: expecting SSH2_MSG_NEWKEYS
> debug1: SS
12 matches
Mail list logo
