For OS X, use mach_absolute_time, described here: https://developer.apple.com/library/mac/qa/qa1398/_index.htm...
846 karma · joined September 25, 2013
For OS X, use mach_absolute_time, described here: https://developer.apple.com/library/mac/qa/qa1398/_index.htm...
The reason being that autocorrelation (and convolution in general) is meaningful when the input signal is linear time invariant. Read more about that here: https://en.wikipedia.org/wiki/LTI_system_theory#Impulse_resp...
If I have time this summer, I'll implement the Gamma and Beta functions, and their inverses, with a permissive license.
The page linked for "our criteria" doesn't mention any criteria other than:
We need tools that a broad community of experts can get behind.
I don't know of a single expert that would recommend Pidgin. I strongly recommend against it, whether you believe you are a "specific target of surveillance" or not.
https://developer.apple.com/library/prerelease/ios/documenta...
That is, unless we support freely-licensed encryption software, financially, rather than just use it.
I believe TrueCrypt was started as a student project, and was no longer worth the effort to the developer(s). For a student or young developer interesting in cryptography, the reward is in the work itself, and in other people using the software. A decade later, though, with less free time, it's much less fun. At that point, a developer could either commercialize their work, or abandon it. TrueCrypt had very little chance of commercial success, since full-disk encryption comes with all new operating systems, so it's been abandoned.
My conclusion is that only for-pay (open-source or not) FDE software can be a viable alternative to TrueCrypt, anything else will eventually be abandoned too. Consider that every project mentioned on this page is based on dm-crypt, part of the Linux kernel, which is supported financially by Intel, HP, and so on. That is a viable, long-term solution, and probably the only one.
But if we want a diversity of cryptography software, we are going to have to start paying for it.
One reason may be that donations to the OpenBSD Foundation are not tax-deductible in the US.
http://www.amazon.com/Introduction-Information-Theory-Symbol...
In the particular case of a series of n equally-probably, independent events, the entropy is given as H = - log 1/n, measured in bits. For example, the entropy of a fair die is - log 1/6 = 2.58 bits per throw.
In this case, the random event is words chosen from a word list. Four words are chosen from fifty thousand, with each word having equal probability of being chosen. So the entropy (measure of randomness) is - log 1/50,000 = 15.6 bits per word, or 62.4 bits per four-word combination. (The script also adds random numbers or symbols, to add up to 90 bits.)
So your recipient would be the only person to download a file of some specific size at some specific time, from a service that only ever served it once. Traffic analysis is how the Tor network is attacked in practice. Unfortunately, Onionshare is more vulnerable to traffic analysis than even the old GnuPG and Dropbox method.
Basically, the French government selectively leaked to a New Zealand journalist, to justify retaliation (tariffs at the EU level, which never materialized) against the US government for burning their Saudi deal.
There has never been any credible evidence that US intelligence agencies pass trade secrets to American companies.
Other than that, Nimrod has been a pleasure to use. If you need a metaprogramming language to generate C, use Nimrod.
If you're curious, the basis of this algorithm is the convolution theorem: https://en.wikipedia.org/wiki/Convolution_theorem
Here is an example implementation of cross-correlation using the FFT, with NumPy:
http://www.eliteraspberries.com/blog/2013/08/application-of-...
http://www.international.gc.ca/controls-controles/about-a_pr...
It's really interesting to read what else is on the list.
Is GetAsyncKeyState still available in Windows Vista? I'm guessing it is, and processes can still read each others' keystrokes without problem. The MSDN documentation doesn't mention it being deprecated. http://msdn.microsoft.com/en-us/library/windows/desktop/ms64...
(By the way this article is from 2011. It would be interesting to read an update.)