Re: Security for various IETF services

John C Klensin <john-ietf@jck.com> Sat, 05 April 2014 05:13 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3112D1A00A8 for <ietf@ietfa.amsl.com>; Fri, 4 Apr 2014 22:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 S4qIsrh1xTvN for <ietf@ietfa.amsl.com>; Fri, 4 Apr 2014 22:12:59 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B70B71A001E for <ietf@ietf.org>; Fri, 4 Apr 2014 22:12:59 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WWIuG-000ECJ-LC; Sat, 05 Apr 2014 01:12:40 -0400
Date: Sat, 05 Apr 2014 01:12:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pranesh Prakash <pranesh@cis-india.org>, Randall Gellens <randy@qti.qualcomm.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF-Discussion <ietf@ietf.org>
Subject: Re: Security for various IETF services
Message-ID: <74F15552A07DC08F9A9822B4@JcK-HP8200.jck.com>
In-Reply-To: <533F3AD5.6000408@cis-india.org>
References: <533D8A90.60309@cs.tcd.ie> <533DF52E.5020707@cis-india.org> <p06240605cf63c268e7df@[99.111.97.136]> <533F3AD5.6000408@cis-india.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Ybu02S02MGobREPaaCRhOVgiUNc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 05 Apr 2014 05:13:04 -0000

--On Friday, April 04, 2014 19:05 -0400 Pranesh Prakash
<pranesh@cis-india.org> wrote:

> Randall Gellens <randy@qti.qualcomm.com> [2014-04-03 19:00:18
> -0700]:
>> At 7:56 PM -0400 4/3/14, Pranesh Prakash wrote:
>> 
>>>>  However, as there are numerous legacy tools that have been
>>>>  built that require access via cleartext
>>> 
>>>  Could you please expand on this?  What kinds of legacy
>>>  tools is that statement talking about?
>> 
>> I have a number of tools and scripts that access IETF and RFC
>> Editor documents and information using HTTP and FTP.
> 
> And these tools and scripts will stop working if HTTPS or FTPS
> are used?    Can these tools and scripts not be made to
> work/compile with NSS / GnuTLS / OpenSSL?  Or is it just that
> it is easier not to deal with encryption?

I can't speak for Randy's, but, for the ones I use, yes, they
will stop working.  And, no, I don't have access to source or
other arrangements that would permit me to recode and recompile
them.

> Curl, wget, and even the perl-based Twitter client I use
> (ttytter) all work just fine with SSL, so I'm curious what
> tools and scripts have trouble using encryption.

See my earlier message.
    john