Re: Call for Community Feedback: Retiring IETF FTP Service

Keith Moore <moore@network-heretics.com> Tue, 17 November 2020 16:34 UTC

Return-Path: <moore@network-heretics.com>
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 D29A33A149D for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 08:34:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 KA7YC52Ktll5 for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 08:34:39 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DEC33A149B for <ietf@ietf.org>; Tue, 17 Nov 2020 08:34:39 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id C02F25C02B2; Tue, 17 Nov 2020 11:34:38 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 17 Nov 2020 11:34:38 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=OIPH4AY5RIl5IzwgeS2Ay+wQWyhke/nUQSTzg4k6L vk=; b=Vewsdv4znz5tIa3tBq86UZNAStugFkDj4EMMJoM/31Wwliu2w6G/oAnZD eL56HiVGAPxm+a7/mjGc4JIdYWZbaz8aG7dz8af0loIeMEJ0yemRHO/2Hasy0hAV 5eau2e6PGRMpjoVgIBN0iSioW+37CO25ltDFw2KQMn0sZWq4NqfnbH5lwyFbD289 XxjGIDsiXJEFG+RQUNHYQQFYiHoMSAL3QQZfNFRGxD/Ql6N5UNjbMdwG2vnVBDxc PpsSxC5Elz0xmTHWSEsVcJ5yeFyKDIc6aq1e5/SlEjIoPYwXEkPuGB4945ePxzlK hM3uR/mAxJVWHamZ4j3WEIAnLWDdw==
X-ME-Sender: <xms:nvuzX2gVioJrw8xxL2Q_8YLGH3R5ZB1q1-xo-lWENManS2CgLSPHKQ> <xme:nvuzX3Cp3NdA6g5_bquDIV6WwdDfmKApZxfoYApqg-oLFOkg1c__plZZhAi7GlJe2 KajmiIb743S9g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudeffedgledtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomhepmfgvihht hhcuofhoohhrvgcuoehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh eqnecuggftrfgrthhtvghrnhephefhuedtheefgfefgffhkeehgfeugfeiudeugeejkeef leelueeiffetfeeuudeunecukfhppedutdekrddvvddurddukedtrdduheenucevlhhush htvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:nvuzX-Ecz3PqHffjacIZnJKF9lKHKOzbEc-bmmMe6C-8_E-5oyaE2Q> <xmx:nvuzX_TdcGVn-L5vIR3fK4RbW-VkVjlvmKz8QrHKM6f149Ky-7vLhw> <xmx:nvuzXzx9qwn2fZZELUsAl23GO8JOttic4E15dncZCBJAf2ElkLPDIA> <xmx:nvuzXy_FcNPuuIxM6CIu1B88TVgY5TyyMj_X5-htFSCJsF_Wvl-opQ>
Received: from [192.168.1.85] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id E0DE23280063; Tue, 17 Nov 2020 11:34:37 -0500 (EST)
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
To: "Livingood, Jason" <Jason_Livingood@comcast.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <0D41F3FD-BA1F-4716-A165-4FE7529431A9@vigilsec.com> <D26DCBB6-3997-4A73-BB46-867B4FD79BD2@eggert.org> <27b80ed2-76fb-aee7-f22d-de56019e9aa9@nostrum.com> <a8bdd67a-13ea-4433-aa38-9cfd48ea28da@network-heretics.com> <0e875497-9986-a0d9-8354-3eac26b7f882@nostrum.com> <a02e15f2-34fb-4124-7ba0-c0ee0070b39f@network-heretics.com> <6a29096e-c76e-9bde-388c-bf411b235346@nostrum.com> <6ff3c8a8-57c9-a278-51ce-ce24fd2dfc0e@network-heretics.com> <01RS3W7DNPHA005PTU@mauve.mrochek.com> <27622517-8EC3-44D1-BB21-1F2071BCA2C2@cable.comcast.com> <5dc7b0d1-d565-92c5-293e-093040596f35@network-heretics.com> <4b46fe4f-0b5b-dbf4-9bd5-f0a4a6ee30c9@nostrum.com> <9b8787b0-af20-0155-6098-7725317084b0@network-heretics.com> <83E1249B-98B8-4D0E-AB78-3D048C691976@cable.comcast.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <463e10a1-3de7-39fb-ee77-f52001e2e2b5@network-heretics.com>
Date: Tue, 17 Nov 2020 11:34:35 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <83E1249B-98B8-4D0E-AB78-3D048C691976@cable.comcast.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T654NCJz9n0LtyTcvCprFLd_-NU>
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: Tue, 17 Nov 2020 16:34:41 -0000

On 11/17/20 11:25 AM, Livingood, Jason wrote:

> On 11/17/20, 11:05 AM, "ietf on behalf of Keith Moore" <ietf-bounces@ietf.org on behalf of moore@network-heretics.com> wrote:
>>     Wow.  That's incredibly arrogant and shortsighted.  I cannot begin to
>      count, for instance, the number of Internet appliances out there (in
>      both consumer and industrial applications) that have http interfaces but
>      do not support https.
>
> [JL] It sounds like those appliances have not had any software updates for many years - perhaps a decade or more. Perhaps they are already compromised or soon will be.

Wow.

There are many environments for which software updates are 
infeasible.     Many devices are deliberately operated on airgapped 
networks, which doesn't mean they're entirely immune to attack but it 
does mean that relying on updates from the net doesn't work.   It's 
extremely expensive to support a low-volume device with security 
updates.   Updates are quite reasonably seen as threats to operations in 
manufacturing environments, where any disruption costs real money, and 
any updates to firmware would require comprehensive retesting of the 
entire system.   And when a device doesn't need frequent updates, any 
update is likely to be done by people who aren't familiar with the code, 
and the chance of introducing more bugs than are fixed is quite high.

So basically, it's completely unrealistic to assume that every device 
should be updated, or that updates improve the security of a device.

Keith