in the wrong order). Fix this, and bump PORTREVISION again. The window
was only a few minutes, but this won't disrupt things, and someone may
have updated in that window given the prominence of the problem.
Obtained from: Matt Power <mhpower@BOS.BINDVIEW.COM> via Bugtraq
silently added on 2000/01/14 as part of the IPv6 support. The default sshd
config had sshd listening both on port 22 and port 722 (this was apparently
intended to facilitate traffic-shaping in that different queueing priorities
could be assigned to ssh sessions on the two ports).
Combine two patches into one.
Submitted by: peter
stopping the server.
Martti's submission did not include -h, which I added because if I had
added the scripts the way he submitted them, the server wouldn't be
started on startup.
PR: 10196
Submitted by: Martti Kuparinen <martti.kuparinen@ericsson.com>
Reviewed by: kris (partially)
No response: maintainers (PR opened February 22, 1999)
Submitted by: Arjan.deVet@adv.iae.nl (Arjan de Vet)
- do not exit in failure to connect using IPv6 and try to IPv4
when connecting to dualstack hosts.
Approved by: torstenb
be added. This is done to support the build on pre 4.0 machines with
the KAME IPv6 stack installed. It has been verified to build+work
with both 4.0 and 3.4+kame.
Org. patch Submitted By: Munechika SUMIKAWA <sumikawa@ebina.hitachi.co.jp>
The IPv6 patch was obtained from the kame repository and has been
been writen by KIKUCHI Takahiro <kick@kyoto.wide.ad.jp>
Due to the whole mess with different patches it was necessary to include
both the IPv6 patch and patch-ssh-1.2.27-bsd.tty.chown in ${PATCHDIR}.
Since both patches modify the configure script it was also necessary
to rebuild it via autoconf from configure.in. I've decided to use
USE_AUTOCONF instead of including the re-build configure script in
${FILESDIR}
Obtained from: KAME/WIDE
Submitted by: Issei Suzuki <issei@jp.FreeBSD.ORG>
Upgrade to 1.2.27.
# I'm not maintainer but it seems that torstenb is too busy to
# look the PR and many people want new version ssh port.
OpenBSD and FreeBSD now both use rresvport. This is a nop for
FreeBSD, but for OpenBSD this picks random port numbers.
Submitted by: deraadt@cvs.openbsd.org
fatal: Local: Agent socket bind failed: Address already in use
It would happen when the server tried to create the Unix domain
socket "/tmp/ssh-username/agent-socket-123", if the file already
existed. It could already exist if it happened to be left over from
a system crash. This patch unlinks the file before attempting the
bind operation.
I will send this patch to ssh-bugs@cs.hut.fi too.
1) pw->pw_class was always zero since not copied
2) login_getuserclass() used instead of login_getclass(), so
default class always returned
3) env pointer can be redefined at the moment of setusercontext() call
regenerated them to fix the line numbers. Also, I added two commented out
options in Makefile, one to tell sshd that a group writeable homedir
is OK because all users are in their own group, and the other is to allow
an unencrypted connection (which is dangerous since it can lead to
compromise of keys), but on a secure network it's damn useful for backups
etc.
ignores it's argument (it's meaningless, the kernel keeps the state), but
2.1.x use it. ssh was effectively giving a random port to 2.1.
Originally noticed by: John Polstra <jdp@polstra.com>
reporting bug which happens if the remote end uses tcp_wrappers to control
sshd access (it says something like "read: no such file or directory" or
"read: permission denied" instead of "connection closed"). I already sent it
in to the ssh mailing list.
Submitted by: fenner
