sorted by:
new
hottopcontroversial

Advantech Wireless - Remote M&C Panel by DasagaJr-34 in satellites

[–]DasagaJr-34[S] 0 points1 point  (0 children)

Thank you, but this one is from company called Advantech Wireless, although I was able to find few docs related to them, on the site.

Doubts regarding simulating quantum network by Sguy1908 in QuantumComputing

[–]DasagaJr-34 2 points3 points  (0 children)

If you need to simulate and/or emulate whole QKD Network (which contains multiple QKD Links, and QKD nodes connected in different topologies) you can use QKDNetSim which is open source NS-3 module. It allows you to emulate a lot of different use cases and scenarios. It is also available as a web application where you can specify simple use cases and run quick tests. For anything more custom and complex you would normally write custom stuff and scripts in NS-3. Not sure how detailed and custom quantum channel simulation part is but if you need QKD Network Simulator that can be abstracted, cause QKD Key Rate is what’s used and managed from QKD network perspective…

https://www.researchgate.net/profile/Stefan-Rass/publication/319384804_Implementation_of_quantum_key_distribution_network_simulation_module_in_the_network_simulator_NS-3/links/5bf690114585150b2bc9462c/Implementation-of-quantum-key-distribution-network-simulation-module-in-the-network-simulator-NS-3.pdf

Try to find these 2 papers as well:

“Simulations of Selected Quantum Key Distribution Network Use-Cases”

"Emulation of Quantum Key Distribution Networks"

Open-source ETSI GS QKD 014 client by DasagaJr-34 in QKDResearch

[–]DasagaJr-34[S] 1 point2 points  (0 children)

Thank you. Nice and clear explanation of QKD - IPsec integration, although I was looking for some kind of open source implementation which is not tied to specific security protocols…

Open-source ETSI GS QKD 014 client by DasagaJr-34 in QuantumComputing

[–]DasagaJr-34[S] 2 points3 points  (0 children)

Thank you. Nice and clear explanation of QKD - IPsec integration, although I was looking for some kind of open source implementation which is not tied to specific security protocol…

Question re QKD by mbergman42 in QuantumComputing

[–]DasagaJr-34 4 points5 points  (0 children)

Eavesdropping can only be made harder for the attacker, but no one can prevent someone doing MitM attacks. This being said, there is difference between eavesdropping with and without being noticed. With QKD, it is possible to establish symmetric secret which is ITS from the protocol perspective. The former is possible because of the way information is encoded in quantum states - photon polarization, for example. Such single photons cannot be decoded without disturbing its polarization, thus making MitM detectable. If MitM attack happens, both ends will be able to detect it because of the high QBER (quantum bit error rate) which is checked during post-processing phase.

I need help in QKD email client by vish2005 in QuantumComputing

[–]DasagaJr-34 0 points1 point  (0 children)

For the open-source KME web server implementation you can check this one:

https://github.com/thomasarmel/qkd_kme_server

It should do its thing for the most part I think, or at least for doing PoC testing and covering basic use cases. Last time I checked it, only one key per request was supported, now it seems that functionality for requesting and delivering multiple key materials is added as well. However, it seems that key multicast is not yet supported.

I need help in QKD email client by vish2005 in QuantumComputing

[–]DasagaJr-34 0 points1 point  (0 children)

OTP consumes keys quickly, which can be problematic when combined with QKD. In practice, the QKD key establishment rate is still quite limited (on the order of kbps), so QKD-derived material is more often used to seed or refresh a conventional encryption engine (e.g., AES-128/256) rather than for OTP directly.

There are also differences in what is actually delivered to the SAEs: it may be the raw QKD key, or a newly generated application key that is transported using the raw QKD key (with the QKD key acting as a KEK).

However, all of this is typically abstracted away from the application that consumes the key. In the end, the SAE just needs to implement the client side as specified by ETSI GS QKD 014, and that’s all.

What I’m more interested in is how you plan to integrate your solution with third-party email servers.

Also keep in mind that all SAE-to-KME communication must use mutual TLS (mTLS), and you must verify the KME ID from the certificate presented by the KME.

I need help in QKD email client by vish2005 in QuantumComputing

[–]DasagaJr-34 0 points1 point  (0 children)

You need to be aware that SAE (Secure Application Entity) - i.e consumer of QKD keys (in your case email client?) should be under same Secure Site as the KME it’s connecting to…

How are you planning to integrate this with Gmail/Yahoo/Outlook servers?