Re: [TLS] SSL cert - CA issuer question - WIndows Event Reporting CA

Bas Westerbaan <bas@cloudflare.com> Wed, 07 June 2023 14:48 UTC

Return-Path: <bas@cloudflare.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 333A1C15199F for <tls@ietfa.amsl.com>; Wed, 7 Jun 2023 07:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_IMAGE_RATIO_02=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1LeuBKvHjJuP for <tls@ietfa.amsl.com>; Wed, 7 Jun 2023 07:48:42 -0700 (PDT)
Received: from mail-yw1-x1131.google.com (mail-yw1-x1131.google.com [IPv6:2607:f8b0:4864:20::1131]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7135C15199C for <tls@ietf.org>; Wed, 7 Jun 2023 07:48:41 -0700 (PDT)
Received: by mail-yw1-x1131.google.com with SMTP id 00721157ae682-568900c331aso85767767b3.3 for <tls@ietf.org>; Wed, 07 Jun 2023 07:48:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; t=1686149320; x=1688741320; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=oVl1vgdxUjnFxBoTYUotqi6y4Qc2d1GRLUuucFkluI4=; b=oqVaB/fXlOM+LkG0waMCPQgETEgm4TqRn+SCBA40PDkVpxfdy41Mip3dfXL3VqKrq0 of3/EajSV2EvbrE4QGlqhTc8YW6M7IWpv9xiRj3McC20eGb8HMRDGHEAcAWXg+S389CC ckdkCPczt1hR6rjGmyDgJ2imiaFj+iVD0Ag14=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686149320; x=1688741320; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=oVl1vgdxUjnFxBoTYUotqi6y4Qc2d1GRLUuucFkluI4=; b=l58C+zRMyDfDw67dmIZDQ6cf85R+sgHqkn+ZhROUOCvRPxYuUE5m9t68j3Hsh8Zimh xJymGq6pOWsQ2AOiHNeeRLRrN2Ha/QN9NFfngfU3CFKQDvrOD7lWabfR3yjLT9fMHLMP HfnDCbZ8KaPnp2fuC+N6qu5PVXguIpJ06E1wY6HE+FKo29T/5xuZpjKtW5FdTwdoq1cz umUKndK6UsXjpR58GRL2G2x7VgxzcXe5KQiVZTY7OH/V36JU9TTDosL/qo20+5EkMxtE iIbBdmksY6L4k2rrUHyQXS5u1HWftLSIuWvewwSXiz1iWRbByuINRZM7JgyXgVX2y688 gO+A==
X-Gm-Message-State: AC+VfDzRj4pqCMTUQsyl3IvLWnpHpE4xGhTUWa6VIartUBQmou4Rw5QZ ZeIBS6hlFpy3GoM0L+e5NBGOKaYqxSlKdaO1eZLXdA==
X-Google-Smtp-Source: ACHHUZ5uFJBJwE2y5/aD8gACJwNUz//CQi4KvV3iD4jujAaDp+HV+inAM0CwQtY89Lj2Ke9PnQm/A0JsguSOL0bn7PE=
X-Received: by 2002:a0d:d552:0:b0:566:c47:d06a with SMTP id x79-20020a0dd552000000b005660c47d06amr6716244ywd.13.1686149319811; Wed, 07 Jun 2023 07:48:39 -0700 (PDT)
MIME-Version: 1.0
References: <CAG5P2e8xQSyBChic=xgqq0FUMfmZXSyXXczb+OkdacthUDZcWw@mail.gmail.com>
In-Reply-To: <CAG5P2e8xQSyBChic=xgqq0FUMfmZXSyXXczb+OkdacthUDZcWw@mail.gmail.com>
From: Bas Westerbaan <bas@cloudflare.com>
Date: Wed, 07 Jun 2023 16:48:28 +0200
Message-ID: <CAMjbhoWvvb8dbs7sXcwgso+VEbxHX0zaWSg=KiT3q0gDEPhXqg@mail.gmail.com>
To: M K Saravanan <mksarav@gmail.com>
Cc: "<tls@ietf.org>" <tls@ietf.org>
Content-Type: multipart/related; boundary="0000000000003ff17505fd8b3bd8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/ijDBgoK398RXfdSR-99nOcwSTRQ>
X-Mailman-Approved-At: Wed, 14 Jun 2023 00:12:44 -0700
Subject: Re: [TLS] SSL cert - CA issuer question - WIndows Event Reporting CA
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jun 2023 14:48:46 -0000

The second certificate is ours. The first is not. Thus on the first
connection, a third party is in the middle (MitM). They must've added a
root certificate to your browser's trust store.

 Bas


PS. That it only happens on the first visit might be because that is over
HTTP/2 whereas subsequent visits are over QUIC, which the interception
software/hardware might not support.

On Wed, Jun 7, 2023 at 3:52 PM M K Saravanan <mksarav@gmail.com> wrote:

> Hi,
>
>
> Off late I noticed a behaviour with many https websites.
>
>
>
> When I first access that website, for e.g. https://www.cloudflare.com
> the issuer CA is shown as “Windows Event Reporting CA”.  When I access the
> same site subsequently, it is showing proper CA as “ Cloudflare Inc ECC CA
> -3”.
>
>
> [image: image.png]
>
>
> [image: image.png]
>
>
>
>
>
>
>
> What is this Windows Event Reporting CA? Why does it show this as CA when
> accessing for the first time?
>
>
>
> With regards,
>
> Saravanan
>
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>