Live data from Hacker News

I don't trust Signal

drewdevault.com

241–250 of 473 posts

Re: I don't trust Signal

#241
post #170

Earlier quoted context omitted.

> The article isn't about bad encryption though. It's not about a flaw in the signal protocol or something like that. It's stuff like Moxie doesn't like F-Droid. Which is not an invalid criticism but I'm not gonna stop recommending Signal over Facebook Messenger because of that. You have to look at the whole system, not just one algorithm that it uses - if any part of the system is secure then the whole is insecure.…

Evidently Facebook themselves don't agree with you, since their "Secret Conversations" feature uses Signal's protocol (many other systems also have equivalent features built out of Signal Protocol, Skype, Google Chat, XMPP ... it's a sort of trend) In terms of how Signal compares to something like Facebook Messenger using HTTPS that's an actual technical question that's worth talking about (whereas "Oh no, Moxie Marl…

> although TLS _can_ authenticate both parties, on the Web today we rarely do that. Instead the web server is authenticated using TLS but the client (a Facebook user) has some crummy HTTP layer authentication, maybe a password like "1LvUrDog" filled into an HTML form field.

I would love to see more use of client certificates, but assuming good password practice is there a real security difference? Either way both parties authenticate themselves to the other.

> Next, Facebook is authenticated to you by its proof of possession of a Private Key corresponding to the Public Key in a certificate from a Trusted Third Party CA. An adversary could corrupt this CA, but hopefully that's difficult.

And hopefully Certificate Transparency would catch them if they did.

> Signal doesn't use passwords. Your device has randomly picked a Private Key, but unlike Facebook you don't have a certificate from a CA, instead you can compare the associated Public Key on your device with that shown for another participant on their phone, if they don't match there's a Man in the Middle. So immediately that's an improvement, no password guessing.

Well, depends what you're trying to verify. Verifying that someone is always using the same device is one choice with its own set of tradeoffs (e.g. many people change devices quite often). Verifying that someone always knows a given password is another. I think tied-to-device keys lose you more than you gain, though I appreciate there's room for disagreement here.

> Signal also has Forward Secrecy. In fact each message sent and received changes the keys used for future messages. As a result an adversary can only eavesdrop by actively impersonating one of the participants. In a two person conversation that's often likely to become obvious pretty quickly whereas passive eavesdropping is undetectable.

You don't have to actively participate as such - you can just forward messages between the two. And Signal's servers are already sitting in the right place to do that.

In theory PFS is a valuable benefit. But the level of compromise needed to incorporate it into a practical system where people want to be able to send offline messages and messages to new contacts who they haven't exchanged keys with beforehand... IMO the resulting level of protocol complexity compromises your security more than the fairly weak guarantees you get out of it in practice are worth. Certainly not when the cost is no federation and identity-tied-to-phone-number.

Re: I don't trust Signal

#242

Earlier quoted context omitted.

How do you defend abused spouses in discourse by comparing their needs to people hunted by the most powerful political forces? Surely these two cases ought not be on the same table for comparison.

The original autor outright dismissed the entire class of threats, which, while they may seem "lesser," are also far more common. And it's not just abusive exes, not even every state actor has access to an NSA. Neither Signal nor any other existing application based by the same protocol (which exist and are _more_ popular than Signal itself — What's App is one, for example) are sufficient, but on the other hand, it r…

I always give people the "Who Uses Tor?" page when they wonder about various threats we're addressing with privacy technology. It has a lot of examples that laypeople will understand. It also counters the "only used by criminals" myth that some believe. It also has examples of law enforcement depending on these technologies. That counters the follow-up claim that encryption or privacy tech is just a negative for law enforcement. So, I suggest just giving people the link telling them they'll see many of the benefits. It's worked so far for me.

https://www.torproject.org/about/torusers.html.en

Re: I don't trust Signal

#243

Earlier quoted context omitted.

How do you defend abused spouses in discourse by comparing their needs to people hunted by the most powerful political forces? Surely these two cases ought not be on the same table for comparison.

The original autor outright dismissed the entire class of threats, which, while they may seem "lesser," are also far more common. And it's not just abusive exes, not even every state actor has access to an NSA. Neither Signal nor any other existing application based by the same protocol (which exist and are _more_ popular than Signal itself — What's App is one, for example) are sufficient, but on the other hand, it r…

> not even every state actor has access to an NSA

This is a massively undervalued point. As far as I can tell, most of the people relying on Signal/WhatsApp/Firechat/etc for life-or-death issues are neither hiding from exes nor fleeing the US government. The bulk of use seems to be journalists and protestors in places like Turkey or Bangladesh who have reason to fear state monitoring of communications, but are unlikely to face deep or targeted attacks like having been served a compromised APK from day one.

That Turkey example is seriously relevant. In 2013, the Turkish government created a fraudulent certificate allowing it to intercept traffic to all Google domains, potentially viewing things like gchat and gmail communications. This offered a whole bunch of lessons:

- That the CA web-of-trust model is seriously broken, as we've seen repeatedly.

- That even if companies secure their data and respect your privacy, non-E2E data transfer can still be unsafe.

- That any software or data obtained under a hostile network without a prior signed session is unsafe. Play Store Signal installs in that time could theoretically have been compromised, but "app store versus dedicated download site" and "checksum vs. signature" were irrelevant; all four paths could have been compromised via the same attack vector.

- That "secure download environment, insecure usage environment" is a major, meaningful category of use. That describes a journalist installing Signal in the US and flying to Turkey; an activist installing it prior to a regime change; or a protestor copying it from a trusted friend's installation.

So you're exactly right: Signal isn't a complete solution for an adversary with unlimited resources and direct access to every layer of a network, but it's still massively important even for dealing with most state actors.

Re: I don't trust Signal

#244
post #108

Earlier quoted context omitted.

> Signal is not for state-proof encrypted communication. Not large states like the USA or Russia. If you think it is, you've been misinformed. Ok, but in that case what does Signal offer that any random messenger with transport encryption doesn't? If your threat model doesn't include state actors then you can probably trust a) the HTTPS certificate infrastructure b) an international corporation like Facebook, so you…

1. The HTTPS infrastructure is downgradeable and relies on DNS and a multitude of certificates. And not all the ciphers are safe. Yes it can be done securely-ish, but unless you're layering another level of encryption over HTTPS it isn't fully secure. Layering is what the CIA does, according to the Snowden leaks. 2. As for the rest of it: Cool man, that sounds like you want a normal chat app that is more usable and l…

> The HTTPS infrastructure is downgradeable and relies on DNS and a multitude of certificates. And not all the ciphers are safe. Yes it can be done securely-ish

There's no reliance on DNS. We know what the right way to do HTTPS is, and an app that doesn't have to maintain compatibility with ancient browsers can use a strictly secure profile (no old ciphers, no downgrades etc.). HTTPS is older and more complex than the Signal protocol, but it's also extremely widely deployed and gets a huge amount of attention from security researchers. I think actual attacks on the protocol are less likely with HTTPS than with Signal.

> unless you're layering another level of encryption over HTTPS it isn't fully secure.

Nonsense. Two layers of valid encryption are no more secure than one, and two layers of flawed encryption will almost certainly still be flawed.

> 2. As for the rest of it: Cool man, that sounds like you want a normal chat app that is more usable and less secure. I use Messenger too for things that don't matter.

It's not that my chats don't matter. It's that I don't think autodeletion or one-device-only represent a meaningful security improvement.

Re: I don't trust Signal

#245
> Truly secure systems don’t require trust.

Security is something which only makes sense in relation to an attacker model. Only after you specified that, then we can discuss if something is secure or not.

Signal is not secure if the NSA is after you. Signal is secure if your Chinese competitor is after your business data. Signal is secure if you are a journalist in Turkey.

Re: I don't trust Signal

#246

Earlier quoted context omitted.

My everyday solution is pretty simple. I don't carry a computing device with me. If I do carry a cell phone it's turned off. If I'm in my car I use an old thinkpad laptop and my own 900 MHz wireless network using ubiquiti transceivers and a 30ft pole on my house at home with a custom antenna sticking up out of my vehicle's sunroof. The car's kit re-serves this IP link to my home network over wifi to any devices in th…

Hmm, have you thought about Intel Firmware Support Package (FSP) and Intel ME, that is like baseband on mobiles, and can too read/write to your entire OS installed on your Thinkpad? https://libreboot.org/faq.html#intel Point is, there is no pure platforms today, except probably some Marvell ARM boards with full open source firmware.

I have, quite a bit. Luckily a lot of the intel chipsets can be mitigated with me_cleaner. Additionally, they don't have raw network access since they have to go through my network (and firewalls, transparent and edge) before getting access to anything that's not mine.

The problem with modem baseband cpu and their insecurity is they are the connection and you literally can't watch or mitigate them.

Re: I don't trust Signal

#247
post #90
post #48

Seriously, why do they use the smartphone in the first place? The smartphone ecosystem, be it Android or iPhone, is not secure. It can not be trusted. Even if we avoid Apple and Google's software distribution platform, Your smartphone still has binary blob kernel module, baseband processor and the OS runs on top of that. People who claims secure and trust on top of smartphone are all liar, idiot or both. Don't use th…

Unless it's Librem-5 ( https://puri.sm/shop/librem-5/ ), although we've yet to see what comes out of it

Still not secure. I describe the risks here:

https://news.ycombinator.com/item?id=10906999

Re: I don't trust Signal

#248
post #193

Earlier quoted context omitted.

The F-Droid argument is the strongest and most evident among all. I don't trust Google, I don't trust Play. The main point is, Moxie could take the wind out of the sails of literally all arguments in this page by publishing Signal on F-Droid but he just won't. This alone is enough for me to lose trust in Signal.

Are you going to pay for him to do that?

> Are you going to pay for him to do that?

I donated some money to them a while back. How hard could it be to push the binaries out to a second app store?

Re: I don't trust Signal

#249
post #39

Some version of this post seems to circulate every few months or so. This one is more direct in its accusations of Moxie acting in bad faith. I think this is disingenuous. Moxie has been very clear[0] about the tradeoffs that Signal has made and the reasons for them. It's fine to be dissatisfied with those choices. It's another thing entirely to accuse Moxie of dissimulating. Personally, I'd like to see Signal replac…

Agreed, though personally I find any support of animated gifs in the year 2010 and beyond to be counterproductive.

Re: I don't trust Signal

#250
post #235

Earlier quoted context omitted.

Are you going to pay for him to do that?

And who is paying for Signal to be on Google Play?

google, facebook, whats app, microsoft. Basically the companies that pay for signal end to end encryption in their chat apps.

There are, I'm sure, apps that are better, and that's never been moxie's goal. He's said it over and over that he'd rather have encryption for the masses than the perfect messaging app. It seems disingenuous to assume that he's acting in bad faith when he's clearly doing exactly what he said he wanted to do.

If you want to make the prefect, self-hosted, chat eco system, fire up that matrix server and invite your non tech friends to join. I'm sure that will work out incredibly well.

In the mean time, Moxie seems to realize that to accomplish his goal and make communication incrementally more secure for average users, he needs to go where the users are.

It's crazy to me that people still think that secure communication is a technical problem. We've had GPG for the competent for a long time. The hard problems in secure communication are about using the eco systems that are available to large groups of average users and still being secure.

Post reply on HN