AnaniasAnanas
Joined 8 years ago
Karma
224
Submissions
385
Member since
May 14
Recent submissions
Comment · 7 years ago
Comment · 7 years ago
Nobody was ever fired for using DJB. Meanwhile I would gladly fire someone for using AES128 or the NSA-sponsored curves, despite being in Suite B.
Comment · 7 years ago
> some of them do involve using RSA with absurd key sizes and they'll likely fail the competition.
Only one (specifically DJBs joke Post-QC algorithm), and it did not pass to the second round.
Comment · 7 years ago
> WhatsApp, Telegram and Signal use mobile phone numbers as identifiers
One notable exception (which as I understand is tptacek-approved) is Wire, which only needs an email.
Comment · 7 years ago
> Nobody actually wants to rely on a single entity (for or non-profit) for their communication
You don't have to do that. Protocols like tox for example are distributed and use DHT in order to find peers.
Comment · 7 years ago
It's even worse than it seems. The certificates are only a few megabytes long. https://twitter.com/FiloSottile/status/1145091106138394625
Comment · 7 years ago
Both Signal and Wire are FOSS though.
Comment · 7 years ago
As much as I believe that Efail was the result of badly implemented email clients it's not like the OpenPGP standard hadn't any involvement with it whatsoever. DJB for example suggests small authenticated and encrypted packets, something that OpenPGP does not have. See https://groups.google.com/forum/#!original/boring-crypto/BpU...
Since I am apparently replying too fast and I need to slow down, here is my reply to the child post by Sir_Cmpwn:
> I don't really see the link between the email you posted and efail
GPG decrypts the whole message which might be gigaoctets long and throws it to the output. After it has been decrypted it checks the MDC (if it exists) and throws an error if the MDC does not match or if it is missing. Meanwhile if a OpenPGP message was composed of small authenticated packets GPG would be able to first authenticate if the MAC of the packet is correct and then return an error right away if it does not match. If it did match it would return plaintext and move on to the next packet. You can see now how efail would be prevented, right?
> PGP
Do people use PGP nowadays? I was under the impression that pretty much everyone used GPG ever since it was released.
Comment · 7 years ago
I tried exporting org-mode to latex in the past and found it extremely buggy. I don't really see a reason not to just directly use LaTeX instead.
Comment · 7 years ago
*Everywhere. My own school experience in Europe was pretty much the same as he described. And it is not only my school experience either, there were many cases of unpunished power abuse that the teachers engaged in in nearby schools.
Comment · 7 years ago
The schools that I went to had around 300 students. It did not stop the abuse by teachers nor did it stop the bullying that the teachers ignored.
Comment · 7 years ago
OCaml is very popular in academia though, especially in the field of theoretical computer science and formal verification. Coq, Frama-C, Flow, CompCert, etc are all written in OCaml. Heck, if you are running a graphical GNU distribution chances are that you have installed FFTW, which is written in OCaml. The "industry" is not the only thing that matters when considering the adoption of a language.
Comment · 7 years ago
No offense, I am genuinely curious, why would anyone use any closed source software for anything related to security after the Snowden revelations?
Comment · 7 years ago
Why does everyone seem to hate delay slots? I understand that it makes writing assembly more annoying but most people use a compiler anyway.
Comment · 7 years ago
A better question would be: why were Coinbase employees allowed to use any browser with javascript enabled and outside of a VM? Qubes OS has been a thing for quite a while.
> who only offer certs of RSA and P-{256,384}?
I am pretty sure that nginx and openssl only recently added support for ed25519 certificates. Although to be honest I don't really like the idea of let's encrypt. The addressing system that tor uses has solved that issue already.
> but where most browsers use secp256r1?
This is an issue. Browser vendors should prioritize the djb algorithms.