Re: [Qirg] QKD in OpenSSL

Rodney Van Meter <rdv@sfc.wide.ad.jp> Mon, 18 November 2019 11:56 UTC

Return-Path: <rdv@sfc.wide.ad.jp>
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 AD3681200F7 for <qirg@ietfa.amsl.com>; Mon, 18 Nov 2019 03:56:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sfc.wide.ad.jp
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 8YWb29mhsss7 for <qirg@ietfa.amsl.com>; Mon, 18 Nov 2019 03:56:42 -0800 (PST)
Received: from mail1.sfc.wide.ad.jp (mail1.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:133]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 191F5120018 for <qirg@irtf.org>; Mon, 18 Nov 2019 03:56:41 -0800 (PST)
Received: from [10.125.0.122] (p91006-ipngnfx01marunouchi.tokyo.ocn.ne.jp [153.156.43.6]) (Authenticated sender: rdv) by mail1.sfc.wide.ad.jp (Postfix) with ESMTPSA id B78D77DA1; Mon, 18 Nov 2019 20:56:39 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sfc.wide.ad.jp; s=mail1; t=1574078200; bh=nqNLEQ6+WdfF8Yp4V4ZsyPhKEokGVXLq4BFICK3RlNk=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=UUzokeqnfcYQQqRjnz7mIfkDFhpKcnMXxJfaXF5oWnTpIYtIWZi4veyMkRvML15PU hi5Bq8KCleMddcz319BAnKZvLGq+5z7LCkaHLnt5OaYNBHv+7Mx0i1DsfNGKPDYNwc cDz1WaYDTtfQx2dk6NSOzcBRqgwKMvFP1wZ9Db7AZM8rJIQCsK+nyAruPWV4gFPWFK U55cr3ajLw/Me6aCIcS3HtkusEW89D84/zwKDuJL6M81NhErIw1YIimt3DEgd0y6Ap 9dnSkL58BmqOIgcxeZcB6Jv+4zMky0CBg5vEisUGdia37L3+xrPINhHipiioAVJ7KE rSAwDQkn+6Iag==
From: Rodney Van Meter <rdv@sfc.wide.ad.jp>
Message-Id: <C2F3E76B-D424-410D-B2CB-5D94128C77E2@sfc.wide.ad.jp>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A9FB3932-8933-4EEB-AD14-715845F9A41E"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Mon, 18 Nov 2019 20:56:38 +0900
In-Reply-To: <B4D330A6-0DF8-4846-B16D-518BFC51E0B6@telefonica.com>
Cc: Rodney Van Meter <rdv@sfc.wide.ad.jp>, Bruno Rijsman <brunorijsman@gmail.com>, "qirg@irtf.org" <qirg@irtf.org>
To: "Diego R. Lopez" <diego.r.lopez@telefonica.com>
References: <331F2FAA-6B26-40E7-BE68-379943AECF8F@gmail.com> <9E1CC1FD-A06E-4996-A2A7-EEE618BBFB78@sfc.wide.ad.jp> <A18993AF-F31A-4B4F-BEF6-E9CC474241D2@gmail.com> <B4D330A6-0DF8-4846-B16D-518BFC51E0B6@telefonica.com>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/qirg/e8mHpymLbngxRaC57FblrWDMJ20>
Subject: Re: [Qirg] QKD in OpenSSL
X-BeenThere: qirg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Quantum Internet \(proposed\) RG" <qirg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/qirg>, <mailto:qirg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/qirg/>
List-Post: <mailto:qirg@irtf.org>
List-Help: <mailto:qirg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/qirg>, <mailto:qirg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2019 11:56:46 -0000

DoS may indeed be the attackers goal, but it could alternatively be an attempt to steal some bits of the key without being detected.  QKD in that sense is a battle of wits^H^H^H^Hstatistics between the attacker and the defender.  I’m not actually an expert on the limits of eavesdropper detection in the presence of noise, privacy amplification, etc.

We can certainly talk about this during the open mic portion of tomorrow’s meeting if you’re in SIN or joining remotely.

Note that I consider integration of Quantum Internet services into the Internet to be within scope for QIRG, but the specifics of security arguments certainly require expertise from the Security Area folks, and could arguably be outside the immediate scope of QIRG.

See you tomorrow.

Rodney Van Meter
Professor, Faculty of Environment and Information Studies
Keio University, Japan
rdv@sfc.wide.ad.jp



> On Nov 18, 2019, at 18:34, Diego R. Lopez <diego.r.lopez@telefonica.com> wrote:
> 
> Hi Bruno,
>  
> It looks I’m becoming the “physical argument” guy in the group, but the fact is that QKD (and I guess quantum communication at large) has to do with physical effects, and we have not achieved (not sure if we eve would) the levels of abstraction and virtualization we see in classical digital environments. So observation in QKD implies physical access, and therefore the capacity of direct physical interference. And, FWIW,  cutting a fiber is always cheaper than any quantum-level observations…
>  
> Be goode,
>  
> --
> "Esta vez no fallaremos, Doctor Infierno"
>  
> Dr Diego R. Lopez
> Telefonica I+D
> https://www.linkedin.com/in/dr2lopez/ <https://www.linkedin.com/in/dr2lopez/> 
>  
> e-mail: diego.r.lopez@telefonica.com <mailto:diego.r.lopez@telefonica.com>
> Tel:         +34 913 129 041
> Mobile:  +34 682 051 091
> ----------------------------------
>  
> On 18/11/2019, 15:08, "Qirg on behalf of Bruno Rijsman" <qirg-bounces@irtf.org <mailto:qirg-bounces@irtf.org> on behalf of brunorijsman@gmail.com <mailto:brunorijsman@gmail.com>> wrote:
>  
> Yes, this is something that has always bothered me about QKD.
>  
> In classical key exchange (e.g. Diffie-Hellman), if an eavesdropper Eve passively observes a key exchange (e.g. by passively tapping a fiber), then Alice and Bob neither need to know nor care that Eve is doing that. Alice and Bob can just use the key “knowing” that Eve (if she is present) cannot determine the shared key by just observing the key exchange (assuming Eve doesn’t have a quantum computer).
>  
> But in QKD, if Eve passively observes the key exchange, then Alice and Bob will detect that Eve has “observed" the key exchange and by doing so Eve has invalidated the key exchange. Hence, Alice and Bob cannot use the shared key and must start over or fall back to classical key exchange, just because Eve was there “observing" the key exchange.
>  
> Just as you say, just “passively observing” a fiber constitutes a Denial-of-Service attack.
>  
> Of course, the terminology “passively observing” is kind of meaningless in quantum mechanics, because observing = interfering. 
>  
> But still, this bothered me a lot, and made me feel that QKD is more “vulnerable” than classical key exchange to DoS attacks.
>  
> The standard defense that I always read in the QKD literature is that if Eve is in a position to passively monitor a link, then she is also in a position to initiate a DoS attack by simply cutting the fiber. So, the argument goes, QKD is no more vulnerable to a DoS attack than classical key exchange.  I am not sure if I agree with that — it does not feel quite right to me.
>  
> — Bruno
> 
> 
>> On Nov 18, 2019, at 7:00 AM, Rodney Van Meter <rdv@sfc.wide.ad.jp <mailto:rdv@sfc.wide.ad.jp>> wrote:
>>  
>> Very cool. 
>>  
>> You might check out some of the work we did five years ago that never made it to RFC.
>> https://tools.ietf.org/html/draft-nagayama-ipsecme-ipsec-with-qkd-01 <https://tools.ietf.org/html/draft-nagayama-ipsecme-ipsec-with-qkd-01>
>>  
>> One interesting, and controversial, topic is what to do when an eavesdropper *does* interfere with a QKD connection.  It’s a great, and easy, DOS attack.  So, should the rekeying stop, and the connection depending on the rekeying be killed when the key lifetime expires?  Or should there be a fallback mechanism of potentially lower security?
>>  
>> This is more of an issue for IPsec, which has rekeying and explicit lifetimes, than for SSL.
>>  
>> Rodney Van Meter
>> Professor, Faculty of Environment and Information Studies
>> Keio University, Japan
>> rdv@sfc.wide.ad.jp <mailto:rdv@sfc.wide.ad.jp>
>>  
>>  
>> 
>> 
>>> On Nov 13, 2019, at 21:47, Bruno Rijsman <brunorijsman@gmail.com <mailto:brunorijsman@gmail.com>> wrote:
>>>  
>>> For those interested, I just posted a report on how we added support for Quantum Key Distribution (QKD) to OpenSSL during the RIPE Pan-European Hackathon at QuTech last week. 
>>>  
>>> http://bit.ly/openssl-qkd <http://bit.ly/openssl-qkd>
>>>  
>>> — Bruno
>>> _______________________________________________
>>> Qirg mailing list
>>> Qirg@irtf.org <mailto:Qirg@irtf.org>
>>> https://www.irtf.org/mailman/listinfo/qirg <https://www.irtf.org/mailman/listinfo/qirg>
>>  
> 
>  
> 
> 
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
> 
> The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
> 
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
> _______________________________________________
> Qirg mailing list
> Qirg@irtf.org <mailto:Qirg@irtf.org>
> https://www.irtf.org/mailman/listinfo/qirg <https://www.irtf.org/mailman/listinfo/qirg>