IETF Logo Mail Archive

Re: Telnet and FTP to Historic

Jared Mauch <jared@puck.nether.net> Thu, 03 December 2020 01:04 UTC

Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEBF83A03F1 for <ietf@ietfa.amsl.com>; Wed, 2 Dec 2020 17:04:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ufg-PQ5iO4eB for <ietf@ietfa.amsl.com>; Wed, 2 Dec 2020 17:04:15 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F170C3A03EE for <ietf@ietf.org>; Wed, 2 Dec 2020 17:04:14 -0800 (PST)
Received: from [10.0.0.155] (unknown [23.138.112.46]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 9A9A7540122; Wed, 2 Dec 2020 20:04:13 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: Telnet and FTP to Historic
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <2f0b8bea-0441-b7a2-803b-2fd526790c19@cs.tcd.ie>
Date: Wed, 02 Dec 2020 20:04:12 -0500
Cc: Michael Richardson <mcr@sandelman.ca>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>, "John C. Klensin" <john-ietf@jck.com>, Carsten Bormann <cabo@tzi.org>
Message-Id: <F684473E-C836-4521-88EF-ABE02DD5CAFC@puck.nether.net>
References: <2f0b8bea-0441-b7a2-803b-2fd526790c19@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: iPhone Mail (18B92)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fmb4dOemI3YqL08KwppVNow11Cw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Dec 2020 01:04:16 -0000

Since when were IETF people operators that used debugging tools?

I end up using telnet daily to connect to route servers to debug what is going on. I don't care who is watching me as maybe they can fix the problem for me I am debugging. 

This thread is some comedy gold though.

Sent from my iCar

> On Dec 2, 2020, at 7:47 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> I don't agree. If we assume the system developer is careless,
> then it's easier to recover from such a careless developer
> if they misused ssh than if they misused telnet I'd say.

v2.23.0 | Report a Bug | By Email