Re: [Sidrops] what to do when the CRL is hosed?

Francisco Javier Moreno Arana <fjarana@nic.mx> Mon, 24 February 2020 23:29 UTC

Return-Path: <fjarana@nic.mx>
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 DA5FA3A1351 for <sidrops@ietfa.amsl.com>; Mon, 24 Feb 2020 15:29:23 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tecmx.onmicrosoft.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 2TR9Rl9CjirP for <sidrops@ietfa.amsl.com>; Mon, 24 Feb 2020 15:29:20 -0800 (PST)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-eopbgr760104.outbound.protection.outlook.com [40.107.76.104]) (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 929E13A154C for <sidrops@ietf.org>; Mon, 24 Feb 2020 15:29:20 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lzR3YhobBGHiDRQD1k/fBnz9OyzRV4h5yg8Z4UR65ciGbXZzc5H9UTwCcAQcw+NYI1ra4ITQCu/x6l/Q2U9WAUZhiwjxIcqsE0UETzVyraS6WbGivpFrQawzqaX1qQ3JvaHEOjTaTKnNl32zaHNr4G6FL8K3eJKhyV2snY6gXWY8R6mMNBaxIorSQeQdSNzXgeZjWURH/rklZAxlJDMyO/j7nhN5F1susdN7HHcHZ+4kqRBTg0gKZTand8gDtHVFuwp0uRJVcDnPLCCh8F78ELNLsRsrByvjdOsXVm9lSViUEv7B0t9h011Wa9ucCYpJXM9n4JB/LxSyvdOzGIxCyw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Sb4oIxzfUKmx8tmQM7eokiAWUsqcqAmw4gRH+Z0OCEk=; b=Ec+spdD9K+gZyL+6FfL5tVUPrLrKXwWaJ9rH8x73ZyO2X1q8PP5OYuUFBYHX9a6OhhWXsSn3/C7iXc2oCZ9VmeSHXteJ23yj4b/fDsaQ0rIciGpynT3ACaW8j+nZf0a4IPjr5PvE9w+Hhr12lBl4ALywU7YZhQ6Cy3PpJHT1x7TJlmXj7Sy0uIWh4par7TNeydJpYTCVn1cbSEB6hk9mKW7LHH92K2RfZl2uL/ksLqbzNs0Zkq9ASTQyLOpLrZIN0EiOkWMLvNgrwZQYYsg8jAi1nLOGuqdUHYxIgW0ee/Qa89FphDV5CfO0NhRa4zRD3+qQ7urF/Sdtmg3+Yb8azA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nic.mx; dmarc=pass action=none header.from=nic.mx; dkim=pass header.d=nic.mx; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tecmx.onmicrosoft.com; s=selector2-tecmx-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Sb4oIxzfUKmx8tmQM7eokiAWUsqcqAmw4gRH+Z0OCEk=; b=f6fTj3tYmlfJlU/yFysMUTFHdyQzhm3yAX2IcFU0T2kvNatoumimKM7KkQNd1ABDdcgdpaMwruIpc/1jHNbMRGh0JO4Ev27p7XU9FVWqgzbEiXGZ1UEdorVr9hto/E+gsXkPhkQdRSCMUUUn1/JWXp2SJTx2vXv8dpEhZ6ZUcYY=
Received: from BYAPR05MB5141.namprd05.prod.outlook.com (2603:10b6:a03:96::13) by BYAPR05MB6536.namprd05.prod.outlook.com (2603:10b6:a03:e4::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.11; Mon, 24 Feb 2020 23:29:19 +0000
Received: from BYAPR05MB5141.namprd05.prod.outlook.com ([fe80::5150:4a0b:8d82:f39]) by BYAPR05MB5141.namprd05.prod.outlook.com ([fe80::5150:4a0b:8d82:f39%6]) with mapi id 15.20.2772.012; Mon, 24 Feb 2020 23:29:19 +0000
From: Francisco Javier Moreno Arana <fjarana@nic.mx>
To: Job Snijders <job@ntt.net>, "sidrops@ietf.org" <sidrops@ietf.org>, "claudio@openbsd.org" <claudio@openbsd.org>
Thread-Topic: [Sidrops] what to do when the CRL is hosed?
Thread-Index: AQHV6yVQn+r/EvWQc0CiGVvWf7UvM6gq2MyAgAAikyY=
Date: Mon, 24 Feb 2020 23:29:18 +0000
Message-ID: <BYAPR05MB5141BE96C2699CDBDA45392CD4EC0@BYAPR05MB5141.namprd05.prod.outlook.com>
References: <20200224151532.GD19221@vurt.meerval.net>, <20200224211531.GB60925@vurt.meerval.net>
In-Reply-To: <20200224211531.GB60925@vurt.meerval.net>
Accept-Language: es-MX, en-US
Content-Language: es-MX
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=fjarana@nic.mx;
x-originating-ip: [189.152.234.205]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 36294a0c-d2ac-4448-b146-08d7b9815eec
x-ms-traffictypediagnostic: BYAPR05MB6536:
x-microsoft-antispam-prvs: <BYAPR05MB653694D35E882E64AF358537D4EC0@BYAPR05MB6536.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 032334F434
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(136003)(376002)(396003)(39860400002)(346002)(366004)(199004)(189003)(2906002)(186003)(33656002)(45080400002)(7066003)(478600001)(6506007)(66446008)(71200400001)(316002)(5660300002)(52536014)(7696005)(9686003)(786003)(81156014)(966005)(64756008)(86362001)(66476007)(76116006)(66556008)(81166006)(66946007)(8936002)(66574012)(110136005)(19627405001)(55016002)(26005)(8676002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB6536; H:BYAPR05MB5141.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: nic.mx does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: ebLbeSBa3pEoWvOW/egnIJtRtclId0iWeDDqg7kebMWJdZ5tmckjnkuAKE3u0WwosHw+tJ8Qu0hCECJdOEzP9BoSKyuqqlaHTh7SIsFbSVflbeUBqWZdlB9fUclwJnOnjnbtRVTZuwuhfZ8t1zu6w3TQbxhQzkXcqhpj4AFiQNUyVGljUNLxmqYhmCGiSRX/ozgLu7RpLQ3/+0ZmgV2EOADlXFYvvT9oH5nfkKGzqhgJCZKF4NYCfD3TcmcNWuM3J+RV/4Yh7lV1rBcaRRq+pG2fyklJeXTwidOA6neV7ah4P5DBAVnAd80bmNpGeIXtuG7X8A102E5LFpKduX5KlXSyGh8ESM7ZMPahmsRDd/jEhJ6XzBsVw9zf2BFrGtZ6fFMEolvaYdsgLGKCmI3Oa/FuU5gbeQB/NkHlF4JYQ4UEklm97HMko8Vbyk5xn4VE7sgf/dTMokxlWP/IaUjDIB4b2ruM2t8JV70iKDxbpgXfI+gw2g83tMMzuKYCs3WtCzJg9HxR87dmlulvZRP44g==
x-ms-exchange-antispam-messagedata: Fo8a0tsP/JKcbR3jkdb+jdGtNKR9FXSfJU3y2YwjEvBuOCtY0cJ+jkHcEU4tsv3Nwt5LMU+QTm2hmDu0ULn9FD+uo7iwjhIw6jkCWsPtXaoVm1gsS+9OJVBYWSRhN6SqA57aajINnYJolFUf1rbHxQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BYAPR05MB5141BE96C2699CDBDA45392CD4EC0BYAPR05MB5141namp_"
MIME-Version: 1.0
X-OriginatorOrg: nic.mx
X-MS-Exchange-CrossTenant-Network-Message-Id: 36294a0c-d2ac-4448-b146-08d7b9815eec
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Feb 2020 23:29:18.9605 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c65a3ea6-0f7c-400b-8934-5a6dc1705645
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 8+/ByuIjE05OKN5qtN+b584j2qyIgcZWg2AkUTj8Q4iXZHjSYSbHETM0A6Pc/q8H
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB6536
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/t_I60iKBZq0e-gGNGtLGnNzvGmw>
Subject: Re: [Sidrops] what to do when the CRL is hosed?
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: Mon, 24 Feb 2020 23:29:24 -0000

Hi there,

We had the same discussion (FORT validator dev team) a few weeks ago, since the RFCs don't clarify the subject. Gladly, after reading this thread, we can say that FORT is currently rejecting those CRLs.

We've noticed the RIPE expired CRL and ~70k prefixes were rejected at that moment.

Regards,
Francisco Moreno
________________________________
De: Sidrops <sidrops-bounces@ietf.org> en nombre de Job Snijders <job@ntt.net>
Enviado: lunes, 24 de febrero de 2020 03:15 p. m.
Para: sidrops@ietf.org <sidrops@ietf.org>rg>; claudio@openbsd.org <claudio@openbsd.org>
Asunto: Re: [Sidrops] what to do when the CRL is hosed?

To reply myself:

In case the CRL expired, or is otherwise somehow invalid; and the cache
validator continues to consider the entire validation tree to be valid
for some purpose, the validator is vulnerable to replay attacks because
the use of unencrypted transport such as rsync (which supported in all
validators, by mandate) give no support to trust anything anymore.  I
think ignoring the CRLs state goes against the entire RPKI trust-model
mindset.

A cache validator MUST consider the certificate have been appeared on
the Certificate Revocation List (CRL) issued by the CA represented by
certificate if the CRL is expired.

While one can argue in different contexts of the application of X509
technology different (more forgiving) policies can apply; in the use
case of RPKI I think we cannot tolerate anything less than to assume the
CA has failed when the CRL is inaccessible or expired. And those running
CA's will want to take careful note of this critical operational aspect.

Cache validator implementations which didn't stop parsing RIPE NCC's
tree today, should be aware they are have a security issue and consider
how to upgrade their validation strategy. I think OpenBSD's rpki-client
was the only one to get it right today.

Of course - in making strong statements like this one I can not afford
to assume I am right, so if you disagree - please tell me how I am wrong
(in detail :-) ).

Kind regards,

Job


On Mon, Feb 24, 2020 at 03:15:32PM +0000, Job Snijders wrote:
> Hi group,
>
> It seems we need guidance and consensus on what to do when the CRL is
> hosed in some way or shape. We have two implementation discrepancies pop
> up recently:
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNLnetLabs%2Froutinator%2Fissues%2F274&amp;data=02%7C01%7Cfjarana%40nic.mx%7C18b6558503814064281c08d7b96eb91c%7Cc65a3ea60f7c400b89345a6dc1705645%7C0%7C0%7C637181757516231674&amp;sdata=M%2BMTjX2M%2BYYM3bsSr%2F%2BgonBy6IKSAqaGU%2F4J%2BqlnZ%2BU%3D&amp;reserved=0
> RIPE NCC's top level CRL expired this weekend
> (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ripe.net%2Fsupport%2Fservice-announcements%2Frpki-infrastructure-issues&amp;data=02%7C01%7Cfjarana%40nic.mx%7C18b6558503814064281c08d7b96eb91c%7Cc65a3ea60f7c400b89345a6dc1705645%7C0%7C0%7C637181757516241663&amp;sdata=s3%2F6i%2BhO4bnqncsSj56ZpXDsulvgWUYA13Nm5%2BmnQiM%3D&amp;reserved=0)
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.nlnetlabs.nl%2Fpipermail%2Frpki%2F2019-December%2F000109.html&amp;data=02%7C01%7Cfjarana%40nic.mx%7C18b6558503814064281c08d7b96eb91c%7Cc65a3ea60f7c400b89345a6dc1705645%7C0%7C0%7C637181757516241663&amp;sdata=8AHf2i8DNdTjlU6TnGkbnkXK%2BLyIP%2FN3bnr0GlSZ%2B3E%3D&amp;reserved=0
>
> OpenBSD's rpki-client uses the x509 certificate validation functions
> that come from libressl, which doesn't have a button to turn off only CRL
> timestamp verification. I was told that some nasty code would be
> required to work around that, so one can argue that rolling things by
> hand in X509 handling rarely is a great idea.
>
> One could also argue that a softer landing is needed, unavailability of
> the CRL should mean that only the CRL itself is not available and
> proceed to validate the tree without the revocation list. I can see how
> that is helpful in some circumstances.
>
> So, what to do? Whatever it is, ideally all validators follow a similar
> process.
>
> Kind regards,
>
> Job

_______________________________________________
Sidrops mailing list
Sidrops@ietf.org
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fsidrops&amp;data=02%7C01%7Cfjarana%40nic.mx%7C18b6558503814064281c08d7b96eb91c%7Cc65a3ea60f7c400b89345a6dc1705645%7C0%7C0%7C637181757516241663&amp;sdata=X8IkntXgxnt345fIIKgQEBc%2FpGuLzjtyiwa59Bf2VMM%3D&amp;reserved=0

Este mensaje contiene informaci?n confidencial y se entiende dirigido y para uso exclusivo del destinatario. Si recibes este mensaje y no eres el destinatario por favor elim?nalo, ya que difundir, revelar, copiar o tomar cualquier acci?n basada en el contenido est? estrictamente prohibido. Network Information Center, S.A. de C.V., ubicado en Ave. Eugenio Garza Sada 427 L4-6 Col. Altavista, Monterrey, M?xico, C.P. 64840 recaba tus datos personales necesarios para: la prestaci?n, estudio, an?lisis y mejora del servicio, la realizaci?n de comunicaciones y notificaciones; la transferencia y publicaci?n en los casos aplicables; el cumplimiento de la relaci?n existente; as? como para la prevenci?n o denuncia en la comisi?n de il?citos. Si eres colaborador o candidato a colaborador de NIC M?xico, tus datos ser?n utilizados para: la creaci?n y administraci?n de tu perfil como profesionista; el otorgamiento de herramientas de trabajo; la realizaci?n de estudios; el otorgamiento de programas y beneficios para mejorar tu desarrollo profesional; la gesti?n y administraci?n de servicios de pago y/o n?mina; as? como para contacto y/o notificaciones. Si participas en promociones o en estudios podr?s dejar de participar. Para mayor informaci?n revisa el Aviso de Privacidad<http://www.nic.mx/es/NicMx.AvisosDePrivacidad>.


This message contains confidential information and is intended only for the individual named. If you are not the named addressee please delete it, since the dissemination, distribuition, copy or taking any action in reliance on the contents is strictly prohibited. Network Information Center, S.A. de C.V., located on Av. Eugenio Garza Sada 427 L4-6, Col. Altavista, Monterrey, Mexico, CP 64840 collects your personal data which is necessary to: provide, research, analyze and improve the service; send communications and notices; transfer and publish your personal data when applicable; fulfill the existing relationship; prevent or inform in the commission of unlawful acts or events. If the data is processed in your quality of candidate or collaborator of NIC Mexico, the purpose of treatment is to: create and manage your profile as a professional; provide you with working tools; conduct studies; grant benefits and programs to enhance your professional development; manage and administrate payment services and/or payroll; as well as to contact you. If you participate in promotions or surveys you may stop or quit your participation at any time. For more information read the Privacy Note<http://www.nic.mx/es/NicMx.AvisosDePrivacidad>.