Re: [Sidrops] adopt draft-ymbk-sidrops-rpki-has-no-identity please

Randy Bush <randy@psg.com> Wed, 24 March 2021 02:25 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0DA23A1DA1 for <sidrops@ietfa.amsl.com>; Tue, 23 Mar 2021 19:25:41 -0700 (PDT)
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_HELO_NONE=0.001, SPF_PASS=-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 lsSPlAUp4nQD for <sidrops@ietfa.amsl.com>; Tue, 23 Mar 2021 19:25:40 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B50383A1DA0 for <sidrops@ietf.org>; Tue, 23 Mar 2021 19:25:40 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1lOtD9-0006R2-Jt; Wed, 24 Mar 2021 02:25:31 +0000
Date: Tue, 23 Mar 2021 19:25:31 -0700
Message-ID: <m2mtutz3s4.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: George Michaelson <ggm@algebras.org>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, SIDR Operations WG <sidrops@ietf.org>
In-Reply-To: <CAKr6gn2BWm0ZwuqwLc=g7FXgqbt0eqJ3tWJW7BzP=vEn6qCEcA@mail.gmail.com>
References: <m2ft0sgwfy.wl-randy@psg.com> <alpine.DEB.2.20.2103231615441.21528@uplift.swm.pp.se> <m2pmzpz41r.wl-randy@psg.com> <CAKr6gn2BWm0ZwuqwLc=g7FXgqbt0eqJ3tWJW7BzP=vEn6qCEcA@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/cf8nSD94JvzCEdz2TZwJERKdbuo>
Subject: Re: [Sidrops] adopt draft-ymbk-sidrops-rpki-has-no-identity please
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2021 02:25:42 -0000

>>> When someone asks me to put a string into a webserver file or into my
>>> DNS zone file to "prove" I have administration access, they don't want
>>> to identify me, they just want me to prove I already have access to
>>> the resource at the "business end" of it.
>>
>> usually because dns is the purpose of the exercise
>>
>>> RSC is the same thing, I prove I can create ROAs and/or RSCs
>>
>> as sra would say, you can demonstrate that the same unknown attacker
>> can create objects.
> 
> The attacker has access to private keys behind the specific INR. We
> have bigger problems than the one here, Surely?

indeed.  some are proposing to grant them access to someone's bank
account because they can sign some roa

> (or, can you show me the attack vector, which does not imply loss of
> privacy over a public-private keypair?)

we have been over this multiple times, george.  read the draft

randy