9 Aug
2018
9 Aug
'18
5:14 p.m.
Hi,
Did anyone manage to connect to tweenex,org through ssh now that telnet
port is closed ?
I received an mail that says :
TELNET access to twenex.org has been changed to only support SSH via the
SSH passthru user twenex at sdf.org.
without saying which password should be used ...
Thanks
--
??phane tsacas
10 Aug
10 Aug
5:09 a.m.
On Fri, Aug 10, 2018 at 02:14:54AM +0200, St?phane Tsacas via cctalk wrote:
Did anyone manage to connect to tweenex,org through
ssh now that telnet
port is closed ?
I received an mail that says :
TELNET access to twenex.org has been changed to only support SSH via the
SSH passthru user twenex at sdf.org.
I can connect to that just fine with the standard OpenSSH client:
abuse at panda:~$ ssh twenex at sdf.org
Trying 205.166.94.130...
Connected to 205.166.94.130.
Escape character is 'off'.
TWENEX.ORG, PANDA TOPS-20 Monitor 7.1(21733)-4
If new, type 'new new' ..
@
without saying which password should be used ...
You don't need a password, at least not for the ssh session.
7:14 a.m.
On Fri, Aug 10, 2018 at 6:09 AM, Peter Corlett via cctalk <
cctalk at classiccmp.org> wrote:
On Fri, Aug 10, 2018 at 02:14:54AM +0200, St?phane
Tsacas via cctalk wrote:
% ssh -v twenex at sdf.org
OpenSSH_7.7p1, OpenSSL 1.0.2o-freebsd 27 Mar 2018
debug1: Reading configuration data /home/imp/.ssh/config
debug1: /home/imp/.ssh/config line 47: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to sdf.org [205.166.94.16] port 22.
debug1: connect to address 205.166.94.16 port 22: Network is unreachable
ssh: connect to host sdf.org port 22: Network is unreachable
%
I wonder why I get a different IP address?
Warner
Did anyone manage to connect to tweenex,org
through ssh now that telnet
port is closed ?
I received an mail that says :
TELNET access to twenex.org has been changed to only support SSH via the
SSH passthru user twenex at sdf.org.
I can connect to that just fine with the standard OpenSSH client:
abuse at panda:~$ ssh twenex at sdf.org
Trying 205.166.94.130...
Connected to 205.166.94.130.
Escape character is 'off'.
TWENEX.ORG, PANDA TOPS-20 Monitor 7.1(21733)-4
If new, type 'new new' ..
@
without saying which password should be used ...
You don't need a password, at least not for the ssh session
8:12 a.m.
On Aug 10, 2018, at 10:14 AM, Warner Losh via cctalk
<cctalk at classiccmp.org> wrote:
On Fri, Aug 10, 2018 at 6:09 AM, Peter Corlett via cctalk <
cctalk at classiccmp.org> wrote:
Interesting. I get the same address as you do. I double checked with some other DNS
servers -- 8.8.8.8 is an easy one to remember and reliably reachable. They all show the
.16 address.
But I can connect just fine, so it seems that you have a connectivity issue somewhere on
the path. Traceroute to the rescue?
paul
On Fri, Aug 10, 2018 at 02:14:54AM +0200,
St?phane Tsacas via cctalk wrote:
% ssh -v twenex at sdf.org
OpenSSH_7.7p1, OpenSSL 1.0.2o-freebsd 27 Mar 2018
debug1: Reading configuration data /home/imp/.ssh/config
debug1: /home/imp/.ssh/config line 47: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to sdf.org [205.166.94.16] port 22.
debug1: connect to address 205.166.94.16 port 22: Network is unreachable
ssh: connect to host sdf.org port 22: Network is unreachable
%
I wonder why I get a different IP address? Did anyone manage to connect to tweenex,org
through ssh now that telnet
port is closed ?
I received an mail that says :
TELNET access to twenex.org has been changed to only support SSH via the
SSH passthru user twenex at sdf.org.
I can connect to that just fine with the standard OpenSSH client:
abuse at panda:~$ ssh twenex at sdf.org
Trying 205.166.94.130...
Connected to 205.166.94.130.
Escape character is 'off'.
TWENEX.ORG, PANDA TOPS-20 Monitor 7.1(21733)-4
If new, type 'new new' ..
@
without saying which password should be used ...
You don't need a password, at least not for the ssh session
7:16 p.m.
Thank you for all the answers.
It seems that waiting a day or so solved the problem, and now ssh doesn't
ask for tweenex password and act like a pass thru, as documented.
One explanation why we see 2 adresses might be because the first one is the
proxy/pass thru server, and the second one the host :
ssh -v twenex at sdf.org
OpenSSH_7.7p1, OpenSSL 1.0.2o 27 Mar 2018
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to sdf.org [205.166.94.16] port 22. // proxy (pass thru)
server
...
Authenticated to sdf.org ([205.166.94.16]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions at openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype hostkeys-00 at openssh.com
want_reply 0
Trying 205.166.94.130...
Connected to 205.166.94.130. // host address
Escape character is 'off'.
TWENEX.ORG, PANDA TOPS-20 Monitor 7.1(21733)-4
Le ven. 10 ao?t 2018 ? 17:13, Paul Koning via cctalk <cctalk at classiccmp.org>
a ?crit :
% ssh -v twenex at sdf.org
OpenSSH_7.7p1, OpenSSL 1.0.2o-freebsd 27 Mar 2018
debug1: Reading configuration data /home/imp/.ssh/config
debug1: /home/imp/.ssh/config line 47: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to sdf.org [205.166.94.16] port 22.
debug1: connect to address 205.166.94.16 port 22: Network is unreachable
ssh: connect to host sdf.org port 22: Network is unreachable
%
I wonder why I get a different IP address?
Interesting. I get the same address as you do. I double checked with
some other DNS servers -- 8.8.8.8 is an easy one to remember and reliably
reachable. They all show the .16 address.
But I can connect just fine, so it seems that you have a connectivity
issue somewhere on the path. Traceroute to the rescue?
paul
--
??phane tsacas
On Aug 10, 2018, at 10:14 AM, Warner Losh via
cctalk <
cctalk at classiccmp.org> wrote:
On Fri, Aug 10, 2018 at 6:09 AM, Peter Corlett via cctalk <
cctalk at classiccmp.org> wrote:
> On Fri, Aug 10, 2018 at 02:14:54AM +0200, St?phane Tsacas via cctalk
wrote:
>> Did anyone manage to connect to
tweenex,org through ssh now that telnet
>> port is closed ?
>> I received an mail that says :
>> TELNET access to twenex.org has been changed to only support SSH via
the
SSH passthru user twenex at sdf.org.
I can connect to that just fine with the standard OpenSSH client:
abuse at panda:~$ ssh twenex at sdf.org
Trying 205.166.94.130...
Connected to 205.166.94.130.
Escape character is 'off'.
TWENEX.ORG, PANDA TOPS-20 Monitor 7.1(21733)-4
If new, type 'new new' ..
@
without saying which password should be used ...
You don't need a password, at least not for the ssh session
2325
days inactive
2326
days old
4 comments
4 participants
participants (4)
-
abuse＠cabal.org.uk -
imp＠bsdimp.com -
paulkoning＠comcast.net -
stephane.tsacas＠gmail.com