IETF Logo Mail Archive

[Qirg] Re: questions about QKD

"touch@strayalpha.com" <touch@strayalpha.com> Tue, 04 June 2024 14:28 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: qirg@ietfa.amsl.com
Delivered-To: qirg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19E4CC14F6A6 for <qirg@ietfa.amsl.com>; Tue, 4 Jun 2024 07:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 OARLEO-oiHHv for <qirg@ietfa.amsl.com>; Tue, 4 Jun 2024 07:28:15 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 AB48DC14F69E for <qirg@irtf.org>; Tue, 4 Jun 2024 07:28:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=AQHgLfi1Ug9U69lkSjPcaGVqv3t80bc3EgmQ7ypd7Ts=; b=mk0jSYBXC+jt4eEcLWY7Se6k1J fWTynciTyfr/dvblUqgvmwDkMuLOwxkC806G4kgsl9k67Ag29zK39nsO5FIEVBnFH98PatU78X1Ch p0Mj1w7rzqSTqUmqmLuiXSsrdk63sE5NaMkh5pvNeW3GEzIrM1uvAs3a5dQ3gex0LoGQ3duahgB5d bT/csiBD3aIG0izMs7wQ0xNxGdgSH1RS2fds9bFShefouUZwHRCSU+MtHfDfy5Hx+XkVzIv6kdmG7 twtH/l9XQDI6wH8jkEimeQyMtwRqTGd5n72hUOa5eNYxaFUWvN/zcue8sjkX5zAi0wAbzOxzYNP2q tBLWLSfg==;
Received: from [172.58.211.174] (port=25079 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from <touch@strayalpha.com>) id 1sEV94-008YVq-0L; Tue, 04 Jun 2024 10:28:14 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_52960D47-D856-4D4D-8149-C45DF00C2145"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <b856e6c3-709b-4eb5-8de6-1cff419a74e2@sfc.wide.ad.jp>
Date: Tue, 04 Jun 2024 07:28:02 -0700
Message-Id: <698D6D38-2415-4695-BA93-2261CCF1C262@strayalpha.com>
References: <6fb0218c-1ce0-4fb8-a0ee-14347c357f29@sfc.wide.ad.jp> <GVXPR07MB96788AB065A0C97E6A976E7589F82@GVXPR07MB9678.eurprd07.prod.outlook.com> <b856e6c3-709b-4eb5-8de6-1cff419a74e2@sfc.wide.ad.jp>
To: Rod Van Meter <rdv=40sfc.wide.ad.jp@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3774.600.62)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Message-ID-Hash: NZAFEH7ZJO3QK3GHVRDGJAFS2J2THWPH
X-Message-ID-Hash: NZAFEH7ZJO3QK3GHVRDGJAFS2J2THWPH
X-MailFrom: touch@strayalpha.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-qirg.irtf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>, "qirg@irtf.org" <qirg@irtf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Qirg] Re: questions about QKD
List-Id: Quantum Internet RG <qirg.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/y93xKJnKARlKU_quI5wckMBR3E4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/qirg>
List-Help: <mailto:qirg-request@irtf.org?subject=help>
List-Owner: <mailto:qirg-owner@irtf.org>
List-Post: <mailto:qirg@irtf.org>
List-Subscribe: <mailto:qirg-join@irtf.org>
List-Unsubscribe: <mailto:qirg-leave@irtf.org>

> On Jun 4, 2024, at 12:59 AM, Rod Van Meter <rdv=40sfc.wide.ad.jp@dmarc.ietf.org> wrote:
> 
> The real forehead-slapper is when someone hacks a given QKD system and the response is, "Oh, well, that's just an implementation problem, it's still theoretically secure," as if "theoretically secure" or "it would have been secure if you had implemented it right" systems aren't one of our biggest source of headaches.
> 
FWIW, it might be useful to appreciate this gap in the context of IPsec and actual trusted implementations of IPsec.

The former is in most OSes for free; the latter can cost hundreds of thousands of dollars. It also takes new instances *years* to be certified as trusted, even now.

I.e., the gap is a big issue, but not a uniquely QKD one.

Joe

v2.27.6 | Report a Bug | By Email | System Status