From: ht@cogsci.ed.ac.uk (Henry S. Thompson)
To: Corinna Vinschen <cygwin@cygwin.com>
Subject: Re: [ANN]: Testversion OpenSSH-20001221
Date: Fri, 22 Dec 2000 09:47:00 -0000 [thread overview]
Message-ID: <f5b66kctkjb.fsf@cogsci.ed.ac.uk> (raw)
In-Reply-To: <0012220123340J.10826@cygbert>
Corinna Vinschen <cygwin@cygwin.com> writes:
> I have just uploaded a new version of OpenSSH.
>
> **********************************************************************
> *** Please note that this is a TEST VERSION. ***
> **********************************************************************
I finally noticed something which may explain a lot of the sshd/inetd
problems discussed on the list lately. At the end of the output from
ssh_config, it says "don't forget to change the path to sshd.exe in
the service entry or in inetd.conf". When I go to edit inetd.conf, I
find the port 22 entry points to /usr/local/libexec/in.sshd.exe, which
has not been updated by recent releases. Is changing this to
/usr/sbin/sshd.exe the right thing to do?
ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
W3C Fellow 1999--2001, part-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2000-12-22 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-21 16:23 Corinna Vinschen
2000-12-21 16:27 ` Corinna Vinschen
2000-12-22 9:47 ` Henry S. Thompson [this message]
2000-12-22 10:33 ` Corinna Vinschen
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=f5b66kctkjb.fsf@cogsci.ed.ac.uk \
--to=ht@cogsci.ed.ac.uk \
--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).