Re: [sipcore] Enabling the wildcard certificates for SIP TLS implementation

Simon MORLAT <simon.morlat@gmail.com> Tue, 11 August 2020 08:44 UTC

Return-Path: <simon.morlat@gmail.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A59213A0E92 for <sipcore@ietfa.amsl.com>; Tue, 11 Aug 2020 01:44:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=gmail.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 xQke5JY2yZ97 for <sipcore@ietfa.amsl.com>; Tue, 11 Aug 2020 01:44:08 -0700 (PDT)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37C653A0E8D for <sipcore@ietf.org>; Tue, 11 Aug 2020 01:44:08 -0700 (PDT)
Received: by mail-oi1-x22f.google.com with SMTP id l84so11482913oig.10 for <sipcore@ietf.org>; Tue, 11 Aug 2020 01:44:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NPdHi3IjushyGVtr6GDBEQF7ujgA9F/lLv46Idp4Y6E=; b=UaTTOku9faDBpfoSg/kt47MvxyeNY7R2nJ5CNOcwePbyvgsHAuMjNEf8PKQwUIfTjC Qx4/I7HvDf3GoxvNujkcUaE5j4v/80j7JcHKbyzgaMfYq5Ib5giU5iTx0/Etrjb+ZuIA YjW+cm+u34tOjbAHyoD68YtC31ehcCJH9/jOxDEuUi1uXtjWa+ia+Y3+hFhmD107M5Vq tkeJn6M2AedAvbWPTrqPlNVmrVB02YNRRJ6eVhO9ICdx0KrRh34KyrgSnP5gk7yZ40lK 1C2kj7oKFp25/t7dn8eq/RiQXCCK6U/E6SveuAQTRVTpsepYPIxizKR+hpoN9s5XRVJs jIMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NPdHi3IjushyGVtr6GDBEQF7ujgA9F/lLv46Idp4Y6E=; b=BAo+e5OZBeBrQokeHY5kbFGIk5PjctsTh0WvrcAhi8glk+A4iu3L9njEVnCqubr2be Y4S/yjd1pNWV4NMSD1oy62wWhgUbKDCU2kj99nDcoipkwi4VpXf4af4mXZ6LizslVPcE aTyvDdApMuk0Nf6Fs8jaFNMrQOUSxEMk8gD0B+toiZlmEpQ8GAx0LS4UIlVSA86W8CXu 18enf/HpQKWlqJHHeGDWQdVSNggj0iUCJDwokSjNCilTNsiA4csDYHDRYi4Dscijfk0s +iCkA5urU2vYju0CMdpGQb3MR7Gui29L6pYz4vv6KvraKYxmlibF08pDL7LgHsOTEFQ5 nLhA==
X-Gm-Message-State: AOAM530Mnyxw7EQRszs2P3QNAn7Kfx7sQWfLoB93cxqqNiAvmLZ/WDiZ OR2mf+UyE4FSKgPQ/L4nFFvXKY08UX82HRcLa/YlX4gg
X-Google-Smtp-Source: ABdhPJxkiY3p5LhZVBtIsqy7de+6VlfOiV8dsrycx+2r1sactAQdnVTu2kUg3uqKBLlLSP/5l6oQzhaL2r0T9/aFogc=
X-Received: by 2002:aca:1209:: with SMTP id 9mr2694290ois.136.1597135447291; Tue, 11 Aug 2020 01:44:07 -0700 (PDT)
MIME-Version: 1.0
References: <CAJr_9Tau8iW7idbJLNhhKX5MA5PDhZxR0vmdcfva6_fMMBfKCA@mail.gmail.com> <5BFABAC0-BCF4-4282-A457-F41BD3D142F2@edvina.net> <CAH_g9Rx5DcgOG1--GsUv86OJRu0Kf2MwA-p25gasVa=ex-R95A@mail.gmail.com> <AFF09E0F-3063-4C10-B6D8-221237A46FA8@edvina.net> <CAD5OKxsBGM6+Dmx_YEYcJk2ZbTGi6EC1S+z+9DiyHGb6sQjsFQ@mail.gmail.com>
In-Reply-To: <CAD5OKxsBGM6+Dmx_YEYcJk2ZbTGi6EC1S+z+9DiyHGb6sQjsFQ@mail.gmail.com>
From: Simon MORLAT <simon.morlat@gmail.com>
Date: Tue, 11 Aug 2020 10:43:56 +0200
Message-ID: <CAH_g9RxWXKp8nMtPVzb0bNG5GXgshB-iB9NFE3fUddvFjEmkoQ@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: "Olle E. Johansson" <oej@edvina.net>, SIPCORE <sipcore@ietf.org>, Leonid Fainshtein <leonid.fainshtein@xorcom.com>
Content-Type: multipart/alternative; boundary="000000000000fe7e6a05ac961272"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/_oB3tLI-eTw9Vo1hZ5jiXrECvxI>
Subject: Re: [sipcore] Enabling the wildcard certificates for SIP TLS implementation
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2020 08:44:10 -0000

Hi,

Thank you for all your answers, this is very helpful.
I did not know RFC 6125. Based on these considerations, I would say that
wildcard certificates will probably disappear for all applications in the
next few years.

Best regards,

Simon


Le lun. 10 août 2020 à 20:12, Roman Shpount <roman@telurix.com> a écrit :

>
> On Mon, Aug 10, 2020 at 11:04 AM Olle E. Johansson <oej@edvina.net> wrote:
>
>> I found documentation in RFC 6125 from the “Using TLS in applications”
>> working group.
>> https://tools.ietf.org/html/rfc6125#section-7.2
>>
>
> This section essentially says why wildcard certificates must not be used
> and can only be supported for legacy applications. Not supporting wildcard
> certificates does create a certain degree of pain but given security risks
> should continue to be avoided.
>
> Changes are done by publishing a new RFC, not with Errata. That will open
>> up a whole can of worms, but we need to open it
>> and specify how SIP over TLS should work. Like the "transport=TLS” stuff
>> and deprecating “SIPS:”.
>>
>>
> One thing I've wanted for a long time is an extension which allows to
> multiplex several DTLS connections over the same protocol/address/port
> pair. This will allow to replicate all the current SIP over UDP deployment
> scenarios using a secure protocol. Once this is available, I would
> participate or author an RFC.
>
> Best Regards,
> _____________
> Roman Shpount
>