5 ms·
I don't know that I made any extrodinary claims. You published a spreadsheet listing messaging apps 'ordered by security' in which Signal, Whatsapp and iMessag
by pvg 8y ago
I don't know that I made any extrodinary claims.
You published a spreadsheet listing messaging apps 'ordered by security' in which Signal, Whatsapp and iMessage are shown as way less secure than IRC. It also still says, and you've repeatedly argued here, that things like whether, say, WhatsApp uses E2E encryption is essentially unknowable.
- smbullet 8y agoThe apps listed in the spreadsheet are clearly sorted by number of features supported (with weights). I don't think OP is necessarily claiming IRC is more secure than Signal.
- pvg 8y agoThey are sorted largely by security, according to the author. "It is currently roughly sorted by security. Usability is subjective and people can work down the list to the most secure tool they feel they can comfortably use." https://news.ycombinator.com/item?id=18233721 https://news.ycombinator.com/item?id=18233721
- smbullet 8y agoOops, I guess I missed that comment. Thanks!
- lrvick 8y agoYou are correct. I generalized this as "roughly sorted by security". Some in the list, like Tox, have notable design flaws, but this list is binary and does not account for implementation quality. This is mostly for discovery of options to consider diving into.
- tptacek 8y agoHe's not correct (as he has since acknowledged!), and you did, and still do, suggest that placement on the chart implies greater or lesser security. You literally included instructions on how to read and use the chart that make that point. "Usability is subjective and people can work down the list to the most secure tool they feel they can comfortably use."
- lrvick 8y agoIRC is lacking in features but setup correctly with modern OTR I stand by it having easy to reason about security advantages Whatsapp and iMessage do not. (Usability is another story) Notably if there was a blackbox audit of Whatsapp or iMessage 6 months ago you have no path to easily check if a blatant backdoor was introduced in the build you installed last night. You also can't know if there were obvious flaws in the code the whole time that would be very hard spot in blackbox testing if you didn't know what to look for. Maybe the app build from last night leaks its key intentionally via very subtle steganography in metadata? Compare to a binary I installed via F-Droid that I can confirm was built reproducibly from a given git head I can go see the code review for. To use a simple analogy: I can see the exact ingredients of what went into -my- meal instead of what went into the meal of the food inspector. This allows much deeper release accountability and -is- a major security feature iMessage and Whatsapp lack worth flagging. Verifying security with source code is hard enough. Without source code it is substantially harder and I for one have no interest in using or recommending security tools that fail to be 100% transparent about how they work. Without source code all we have are claims that can never be thoroughly verified.
- tptacek 8y agoYou keep making this argument and ignoring experts who tell you it is bogus. The whole thread is there for everyone to read; you can pretend you haven't read the rebuttals, but you can't pretend for everyone else. The idea that "without source code we can't thoroughly verify things" is false, and at odds with basically all of modern software security.
- lrvick 8y agoOh, I read them. I simply firmly disagree with them and my personal experience of 15+ years finding and fixing security issues flys in the face of your statements. We clearly test software for bugs very differently. I made specific arguments and use cases to justify my position and you have simply told me I am wrong without directly addressing them. Once again, I find the term "expert" overrated. I for one admit I am not an expert on security, a field that is already hard enough on auditors like myself without withheld source code. I have also worked with a half dozen or so security auditing firms all of which stated source code access would make their job much easier. It didn't take me hours of blackbox testing for me to find CVE-2018-9057. It took me 20 minutes of reading code on Github half asleep at 4am because I was curious about an unrelated bug. I remain convinced blackbox testing would of very probably never found that vuln, and even if it did, not in as short of a time period. I trust Terraform over closed alternatives because it was patched within a couple hours of me mentioning it on IRC by a peer who submitted the bug report and patch in one shot. I could verify the source code fix easily and compile the new binary myself to take advantage of the patch before Hashicorp even merged it. I can also easily verify there are no regressions in future releases. Tell me how you go about solving for this or other subtle cases like stego exfiltration more easily -without- source code. Also how you or your team could of patched the issue yourself without source code. If I really solved this the hard way then I will by all means move my security engineering career to focus more on blackbox testing as you seem to be advocating for.