Re: Telnet and FTP to Historic

Michael Richardson <mcr@sandelman.ca> Thu, 03 December 2020 00:41 UTC

Return-Path: <mcr@sandelman.ca>
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 10EB73A02BB for <ietf@ietfa.amsl.com>; Wed, 2 Dec 2020 16:41:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 q8qcogc59q-C for <ietf@ietfa.amsl.com>; Wed, 2 Dec 2020 16:41:38 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 457613A0100 for <ietf@ietf.org>; Wed, 2 Dec 2020 16:41:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 37CF2389B8; Wed, 2 Dec 2020 19:43:27 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id PdjvBRt36Wta; Wed, 2 Dec 2020 19:43:26 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id AF75E38983; Wed, 2 Dec 2020 19:43:26 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 86434B54; Wed, 2 Dec 2020 19:41:36 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
cc: Mark Andrews <marka@isc.org>, "Scott O. Bradner" <sob@sobco.com>, "John C. Klensin" <john-ietf@jck.com>, Carsten Bormann <cabo@tzi.org>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Telnet and FTP to Historic
In-Reply-To: <db927a1a-a723-93d2-fa47-eb50c3a3fe09@cs.tcd.ie>
References: <AA1E0A8464BC45FB4FA44684@PSB> <2D63A357-E253-462C-864D-2BF96D3E2E18@tzi.org> <F4CD3381C5D0E24C91FC4A91@PSB> <20201201030759.GJ5364@mit.edu> <5720F933910C959C9278EBCF@PSB> <CAMm+LwgpcLxSdzgfJy2441hjNWP=Fui-f8Oq1bZB=2QdZeOUNQ@mail.gmail.com> <0c5a4935-f0b6-4b86-dc0e-3b4466bc09a4@nostrum.com> <F1FF9720-AA72-4B92-ABE7-6E0E875059BA@tzi.org> <16446.1606931808@localhost> <CAMm+Lwj51YLpwZLCxsVeg=6tBwaG845Kg4WN4hbA8Bv=pjjKrQ@mail.gmail.com> <C9D1281FC33DACED4FB385A3@PSB> <6B1BC8E3-913D-4683-A463-AD6099103749@sobco.com> <08035677-a35e-45ed-39e9-b01df6d01010@cs.tcd.ie> <AD188A77-24EA-4C63-B9A8-2F901969269D@isc.org> <db927a1a-a723-93d2-fa47-eb50c3a3fe09@cs.tcd.ie>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 02 Dec 2020 19:41:36 -0500
Message-ID: <28470.1606956096@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/O_-P-r3V4z7NxAvw7cwWsfaHjdg>
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 00:41:43 -0000

Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
    >>> Hiya,
    >>>
    >>> On 02/12/2020 23:19, Scott O. Bradner wrote:
    >>>> I fully agree with John
    >>>> I see no justification to move telnet &/or FTP to historic since they are in use (even if
    >>>> some people would rather that not be the case) and neither presents a clear danger
    >>>> to the proper functioning of the Internet
    >>>
    >>> I gotta wonder about that last. Wouldn't it be credible to
    >>> argue that telnet is in fact a real danger, if one looks at
    >>> all the CVEs that've reported on ports with admin/admin
    >>> access? I'm not sure if it'd be the right thing to do, but
    >>> I do think one can credibly argue that deprecating telnet
    >>> might be worthwhile.
    >>
    >> Default passwords with admin/admin is an orthogonal issue.  It can happen just as
    >> easily with SSH or HTTPS as with TELNET.  Telnet has risks but don’t blame TELNET
    >> for bad password selection.

    > Well, yes and no. With telnet that credential is leaked
    > to everyone listening on the network and with ssh, mostly
    > there's sshd_config that can be used to repair a dodgy
    > initial deployment.

Replacing telnet with ssh and still using passwords that never get changed is
less secure in my opinion.   You mention "sshd_config", but frankly, if you
knew how to do that, then you wouldn't have the problem in the first place.

At least nobody pretends telnet is secure.