lemented yet - strange, in 4-STABLE
> they seem to be working fine. Can someone explain this?
> (or give some URL).
Although not strictly related to your sshd problem, I would like to say
that login classes are implemented, only not all of the knobs that the
manpage describes used to work at
Hi,
I suppose I've found the reason for such a strange sshd
behaviour - the problem is I was using login classes in
my master.passwd. Man for master.passwd says that login
classes aren't implemented yet - strange, in 4-STABLE
they seem to be working fine. Can someone explain this?
(or give some UR
Andrew Thompson wrote:
On Wed, 2002-12-11 at 05:52, Vasyl S. Smirnov wrote:
Hi again.
One more strange thing I've just discovered about sshd - two
example ssh sessions:
1.
> ssh nostromo
Password:
Connection closed by 10.100.76.33
(and the same sig 11/fatal messages on the console)
2.
> ssh
On Wed, 2002-12-11 at 05:52, Vasyl S. Smirnov wrote:
> Hi again.
>
> One more strange thing I've just discovered about sshd - two
> example ssh sessions:
>
> 1.
> > ssh nostromo
> Password:
> Connection closed by 10.100.76.33
>
> (and the same sig 11/fatal messages on the console)
>
> 2.
> >
Vasyl S. Smirnov wrote:
On Mon, Dec 09, 2002 at 12:59:44PM -0800, Kris Kennaway wrote:
On Mon, Dec 09, 2002 at 05:49:31PM +0100, Jens Rehsack wrote:
Can you check the core dump for backtrace and send that?
sysctl kern.sugid_coredump=1
sysctl kern.corefile=/tmp/%N.core (or somewhere else wri
Hi again.
One more strange thing I've just discovered about sshd - two
example ssh sessions:
1.
> ssh nostromo
Password:
Connection closed by 10.100.76.33
(and the same sig 11/fatal messages on the console)
2.
> ssh nostromo
Password:
Password:
Password:
[EMAIL PROTECTED]'s password:
[an
On Mon, Dec 09, 2002 at 12:59:44PM -0800, Kris Kennaway wrote:
> > On Mon, Dec 09, 2002 at 05:49:31PM +0100, Jens Rehsack wrote:
> > > Can you check the core dump for backtrace and send that?
>
> sysctl kern.sugid_coredump=1
> sysctl kern.corefile=/tmp/%N.core (or somewhere else writable by an unp
On Mon, Dec 09, 2002 at 11:11:28AM +0200, Vasyl S. Smirnov wrote:
> [...]
> Dec 9 10:09:05 nostromo kernel: pid 63040 (sshd), uid 0: exited on signal 11
> Dec 9 10:09:05 nostromo sshd[63038]: fatal: buffer_put_cstring: s == NULL
> [...]
Some info I didn't mention in the first post:
The process
On Mon, Dec 09, 2002 at 09:30:32PM +0200, Vasyl S. Smirnov wrote:
> On Mon, Dec 09, 2002 at 05:49:31PM +0100, Jens Rehsack wrote:
> > Can you check the core dump for backtrace and send that?
>
> I doesn't generate a coredump. Any way to enforce it?
sysctl kern.sugid_coredump=1
sysctl kern.corefil
On Mon, Dec 09, 2002 at 05:49:31PM +0100, Jens Rehsack wrote:
> Can you check the core dump for backtrace and send that?
I doesn't generate a coredump. Any way to enforce it?
I've just tried Protocol version 1, and everything was
perfect. I'll try to figure out which part of sshd is
generating th
Vasyl S. Smirnov wrote:
Hi,
Recently I've discovered that I cannot ssh to my box.
After looking at the console, I found the following
messages:
Dec 9 10:09:05 nostromo kernel: pid 63040 (sshd), uid 0: exited on signal 11
Dec 9 10:09:05 nostromo sshd[63038]: fatal: buffer_put_cstring: s == NULL
Hi,
Recently I've discovered that I cannot ssh to my box.
After looking at the console, I found the following
messages:
Dec 9 10:09:05 nostromo kernel: pid 63040 (sshd), uid 0: exited on signal 11
Dec 9 10:09:05 nostromo sshd[63038]: fatal: buffer_put_cstring: s == NULL
It seems to be a bug in
12 matches
Mail list logo
