Re: a dh keys question?
- To: debian-user@lists.debian.org
- Subject: Re: a dh keys question?
- From: Joe <joe@jretrading.com>
- Date: Wed, 1 Aug 2018 08:27:19 +0100
- Message-id: <[🔎] 20180801082719.3deb68e1@jresid.jretrading.com>
- In-reply-to: <Pine.LNX.4.64.1807311748060.5364@server2.shellworld.net>
- References: <Pine.LNX.4.64.1807311128590.26432@server2.shellworld.net> <20180731155743.jex75ctoeot43g57@randomstring.org> <Pine.LNX.4.64.1807311201090.27589@server2.shellworld.net> <20180731162947.nv7unixlhtpysfnq@randomstring.org> <Pine.LNX.4.64.1807311251100.29318@server2.shellworld.net> <20180731193843.yyajsarwvh2gqjiq@randomstring.org> <Pine.LNX.4.64.1807311748060.5364@server2.shellworld.net>
On Tue, 31 Jul 2018 17:49:52 -0400 (EDT)
Karen Lewellen <klewellen@shellworld.net> wrote:
> Hi
> just putting my answer at the top.
> My client does have a log option, will aim for that. still again my
> first priority is finding a place to test with a nonstandard port.
> then I can be sure it really is all about port 22 and 21.
> Kare
>
Do you have access to the client's router? If not, can you ask someone
who does to forward a high port to 22? This is the simplest way of
running sshd on a non-standard port and does not interfere with its
operation on 22. sshd doesn't care about this kind of redirection.
>
>
> On Tue, 31 Jul 2018, Dan Ritter wrote:
>
> > On Tue, Jul 31, 2018 at 01:01:31PM -0400, Karen Lewellen wrote:
> >> Hi again,
> >> Otherwise I
> >> just get a repeat of the same conversation, we do not support your
> >> operating system.
"I'm not paying you to support my operating system, I'm paying you for
a functional Internet connection."
Having said all that, I've often lost contact with an ssh server, but
never seen this kind of error, just a 'timed out' message.
--
Joe
Reply to: