mileswu
Joined 14 years ago
Joined 14 years ago
I'm not sure if there are any alternatives that work any better over long distance. I suppose CERN also has CVMFS [1], which is a read-only caching filesystem that retrieves the files from upstream via HTTP. This works much better, but it is read-only so only satisfies certain use cases.
Unlike classical key distribution, these guarantees derive from fundamental physics laws as opposed to, say, RSA that can be broken given enough computing power/time, and so are unbreakable.
Unfortunately there can be flaws in actual implementations of the BB84 scheme, such as side-channel attacks. E91 [1] (a newer scheme) addresses these flaws and prevents these attacks.
[1] http://journals.aps.org/prl/abstract/10.1103/PhysRevLett.67....
I've been tempted to try it, but can't really think why I'd need it.
[1] http://rowanj.github.io/gitx/ [2] http://jonas.nitro.dk/tig/
There are Python bindings to ROOT (pyROOT) but I've found Python in my experience to be a bit too slow when handling the large (10TB+) datasets.
As an aside, it's interesting how ROOT attempts to provide C++ with some basic reflection[2] and saving of C++ objects to dis. Unfortunately it doesn't necessarily do a very good job of it, but perhaps things will change with ROOT6 as it transitions to being based on clang, as opposed to in-house C interpreter.
[1] http://root.cern.ch/ [2] http://root.cern.ch/drupal/content/reflex
It was submitted to HN (https://news.ycombinator.com/item?id=7715881) by another user, but probably never got traction because the title of the article is very vague.
[1] http://jonas.nitro.dk/tig/ [2] http://rowanj.github.io/gitx/
More info at: https://blogs.msdn.microsoft.com/tzink/2016/05/19/why-does-m...