Worried About the Privacy of Your Messages? Download Signal
nytimes.com
nytimes.com
Signal seems to me to one tool in a large profile to maintain freedom of information dissemination and information gathering activity.
It seems to me that speaking to a large number of people anonymously is not possible with any of the existing tools, Signal included, and it seems that this set of tools is the next set that is needed.
Candidates for this include implementations of "Dining Cryptographer Nets," though there exist scalability and DoSability concerns.
* Blocks of text that start and end with magic numbers are signed in-band in the style of "gpg --clearsign".
* The pubkey pair is automagically created on first use.
For legacy support with existing infrastructure (such as HN):
* When you submit a form with a <textarea>, the plugin provides a UI to sign the contents before submitting the form.
* When browsing a page that contains magic number wrapped text, the text is automagically verified and the key pinned.
* The structure of the signed text should allow the plugin to hide the magic numbers, signature, etc, so the text looks normal.
However, newer software would have other options:
* Define a mapping between the in-band data and a tag structure that holds the same data. This needs to be strictly defined, so it is possible to remove the tag structure and verify the original signed text. This gives full presentation control back to the website, while allowing individual posts on the page to be verified.
The big problem - as usual - is key distribution. In the latter case where it is easy to hide metadata with CSS, the public key can simply be included with the post. Unfortunately, in the legacy case I don't think there's a good way to include two pages of public key in each "--clearsign"d post.
* Websites do weird things with textareas. If it's a plain-ol HTML form, it's pretty easy to intercept and do what you want. It seems most websites intercept button clicks then pass your text around to twenty different JS functions and libraries before doing something useful with it. You wind up writing code to handle edge-cases more than anything else.
* To address your final comment, embedding the pubkey inside the text would defeat the entire purpose. A malicious actor (see recent Reddit controversy) can just create their own pubkey, sign the modified comment with it, and noone would be the wiser.
Some things I discovered, and found worked well:
* Keybase has a fantastic library for generating PGP keypairs in-browser. It really added that extra bit of "magic" to the extension.
* Chrome extensions can get CORS exemptions on a per-website basis, and uploading to a standard SKS keyserver is just a POST request that can be done by Javascript.
* Expanding on the last bullet point, verifying other user's comments was tricky. During development, I just downloaded all keys on the keyserver that were uploaded by my extension on a scheduled interval and stored them in localstorage. Unfortunately, I don't think this would scale.
If anyone is interested in picking up where I left off, I could upload the source to Github.
I'm probably not going to pick it up, but I'd definitely read the source.
> It seems to me that speaking to a large number of people anonymously is not possible with
> any of the existing tools, Signal included
It's peer to peer, but there are intermediate nodes which isolate content storage from those who view it, so neither IP addresses of storage nodes nor IP addresses of content consumers can be determined. Since there is no centralization, there's nobody for state actors to attack, legally or by force. All traffic is encrypted and even the ports are randomized, to avoid state firewalls from determining what the traffic is and blocking it.
I think it's our best hope to distribute large amounts of data to the world and avoid the censorship that many countries already have and that even those of us in the west see looming upon us.
You can learn more about it at https://safenetwork.org/ and https://safenetwork.org/documentation/ and https://safenetforum.org/
In countries that are not democracies, I'm uncertain what to do with your complaint. Would you dismiss giving oppressed people access to literature, news, entertainment, or technical and scientific information, on the premise that the information is unlikely to allow them to affect political change? I don't believe that premise is true, but even if it were, their lives are still made better, which means it's far from meaningless.
But governments do a pretty good job of keeping their secrets now, so in the end, I think this will balance the scales towards private citizens.
I see these two subjects as being inseparable. Before I feel comfortable asserting a dissenting opinion in a public forum, I would much rather discuss the subject among my peers where I don't feel I will be immediately eviscerated for a poorly constructed thought. If I don't feel that I have any privacy, I'm more likely to be subject to chilling effects.
While I certainly emphasize with the anxiety of publicly expressing an unpopular opinion, I believe it is, especially in times like these, your moral duty to endure in spite of the repercussions and speak your mind. Even though I went to Stanford and had direct access to Milgrom's famous prison experiment, the lesson from it didnt hit home until many years later I read this article: https://aeon.co/ideas/the-desire-to-fit-in-is-the-root-of-al...
Now, the phrase "All it takes for evil to triumph is for good men to remain silent" resonates with me.
Speaking out matters. So does when, where, and how you speak out. And that is something best discussed privately.
I'd have much more to say on how privacy and anonymity are inextricably linked, but I'll let the EFF say it: https://www.eff.org/deeplinks/2012/01/right-anonymity-matter...
> This phrase does not mean "All good men should continually natter on". It is also your moral duty to present a cogent argument
What I was trying to say is there will be times where you are not as prepared as you like. It's not about presenting an airtight, cogent argument, it's about having the courage to say something like, "Officer, stop beating the shit out of this guy in a wheelchair. He's clearly isn't resisting and you're being a dick."
NNTP, mixmaster remailers, and mail-to-news gateways.
Old school. Those were the days.
If it's not private, what you say, how you say it and when you say it can be analyzed to identify you.
It's a people problem not a technical one.
A good reason to support Wikileaks.
I'm also not sure I see the connection between 'dissent' and the dissemination of stolen private emails.
I think I'll give to the ACLU instead.
You'd think that the revelations about the NSA, things like the UK law that requires ISPs to collect and store your Internet browsing history would have more people "worried" but yet it's still pretty much a lost cause to try to explain to smart friends why this stuff matters.
The downside of becoming known to the NSA is that you can get caught up as an "associate" in someone's drug, criminal or terrorism investigation, and you had no idea that the person was doing anything like that. You might even have no idea that the person exists, since the NSA is "allowed" to go out some number of degrees of freedom from the supposed suspect.
The downside of becoming known to criminals is that you can fall victim to criminal schemes. You don't even have to be known by name or association, your device just has to be discovered; owning it is the all too easy next step. You can be known by installing malware (see the articles on phone downloaded apps), or by criminals seeing your communication on the open internet and becoming aware of you.
That's what I'd tell my friends, if any of them were still listening.
I don't have a clear idea of what the downside is if the NSA gets my information. So I haven't bothered to download Signal.
I don't mean this in the disparaging way that folks who use "If you have nothing to hide, you have nothing to worry about" do, but the truth is that most people assume that Facebook and Google know a huge amount about them already, and that if the NSA wants to find out about them, so what?
Maybe a better education campaign to convince those people who don't believe that they have anything to hide why they need apps like Signal would be an important first step.
What I want people to consider, frequently, is whether or not we should fight these anti-privacy measures not because anything is wrong now, but because of who might eventually be given access to that information. We should fight to make sure that tools to oppress and enforce terrible regimes aren't freely available, even if we find the current leaders trustworthy. The current administration in the Whitehouse is trying desperately to dismantle the sweeping powers to exercise drone strikes without oversight [3], because the next administration doesn't feel as trustworthy to them.
I don't know that there is any downside to having the NSA know everything about you now. I don't know that it will be a bad idea within the next administration. But I know that it's a bad idea to let any random person have that trust, and I don't know that the election system has enough safeguards to prevent abuse by the next person elected. Or the next. Or the next.
[1] https://www.washingtonpost.com/news/the-switch/wp/2013/08/24...
[2] https://news.ycombinator.com/item?id=13102972
[3] https://theintercept.com/2016/12/06/after-8-years-of-expandi...
More concerning is stuff like the US Democratic National Committee emails showing up on Wikileaks. Being blackmailed, ransomed, or leaked is much more of a real threat for most people than some abstract harm that may be posed by the NSA or some ISP logging.
It seems to resonate much more with the millennial demo, as we can empathize with the struggles of journalists/activists/state-dissidents even though we may see our own data/life as in less need of securing, especially in light of the "Facebook/Google already have it so why bother?" sentiment that gets thrown around.
Rare possibility? Yes. But it’s a possibility. «Nothing to hide, nothing to fear» arguments cannot stand before this sort of scrutiny.
Signal requires Google Play Services on Android. That means it's put simply not a privacy messenger. Yes there's crypto, but it's also tied into Whisper Systems' infrastructure, there's no federation. I use Signal reluctantly, and only on IOS.
Threema, which is popular in parts of Europe (and is what I use to an extent) is well established, but not open source, doesn't do voice chat or federation.
Wire is moving in the right direction with respect to being open source and having lots of good features, but is still not open source.
It's 2016 and our best crypto messenger options are worse than what we had 10 years ago when Skype was peer to peer, or Jabber with federation.
I can understand the reasons for not supporting federation, but I disagree. The Internet was built to be decentralised, literally to withstand nuclear war. A walled garden does not provide us with the redundancy or control the Internet offers.
There are other metadata related issues that pretty much every messenger suffers from but I'll leave this out of the scope of this comment.
What Open Whisper Systems and Wire need to do is open source the server components of their solutions, and try to remove the reliance on servers as much as possible. Only then will we have proper message privacy.
I think it's time we just admitted that everything we type/tap/say into any device, regardless of how it's being wrapped up in transit, is absolutely and irrepairably insecure and we're not going to be able to fix that anytime soon.
Even with really smart crypto or some slick app; what makes you think that your messages aren't just being read by your os? Would you really notice? Why would you assume that the api this app talks to is trustworthy? There's no way to even tell if the code for the client on your device is the same as what's in that repo, as if it would make any kind of difference anyway since we can just load code from anywhere at runtime and you'd probably not even notice.
This whole thing is a fucking stageshow, I can only assume we're here to create an illusion that we still have any kind of security. Why? Is it to get some low hanging fruit/tech amateurs who will trust it and expose themselves? I don't know. But, HN, I don't know why WE aren't admitting this to ourselves or why we defend such obvious ruses.
Well, maybe some of you have signal stock I guess.
It's over, we lost, we have no security, we will probably never be able to reverse that situation, things are getting worse rapidly, we can't even know what any of our devices are really doing anymore (even the switches in your dc, the firmware on the UPS's, whatever), and apps like signal are obviously, to me, impossible to trust and I don't know why that's not obvious to anyone who has spent a moment looking at our situation..
Argh.
We dont have to set the bar that high. Just lower it slightly and we can achieve great success.
Can we make the job of NSA and CIA harder? Not necessarily impossible, just to increase the costs they have to spend on whatever it is they are doing, much higher than it is now.
That would be nice.
We can do that with bitmessage, avoid Signal, use Telegram which means outsource to Russia/KGB - so NSA will for sure need to spend more resources if they want to access your "secure chat" on Telegram.
EDIT: but of course, as you say, the problem is socio systematic - any technical system which can or would be used to subvert the state is a threat to the state and will be neutrialized, by takeover, sabotage, lack of funding, the means the state has are enormous. The list we have of secure or safe systems are still zero. Only another state can go against the state.
For example, it was mandated that GSM had backdoors. Any system used for communication, especially mass/group communication, is not free and not allowed to exist. So simple is that. They even tried to go after the creators of secure systems, wasnt the PGP guy scrutinized?
There are too many places, even on a phone, where anything at all can be hiding and we don't really have any way of ever knowing what's there without stepping through the binaries.. That's even more difficult when we've got dalvik and VM's involved. How many people alive do you think could work out exactly what your mobile does in any one second within say, 6 months? ..
For all we know the thompson compiler backdoor really happens, and so how can you even trust the binaries you're producing?
Do you know anyone who built, for instance the openssl.so on their phone personally? Did that person build it on a machine they trust? How can they trust that machine? A single lib with a nefarious function on the few GB of binaries which ship with your phone is enough to completely negate any 'security' these sorts of apps could provide; even if they were trustworthy to begin with which they're obviously not.
It's a charade, assume everything you do is completely observed, regardless of crypto/apps you use.
Even if you have a fully audited and trustworthy (in your view) OS -- then what about IME? Who says that the CA that issued the certs you trust and talk to isn't also feeding them out to the gov or whatever? Who says your HDD isn't talking to the zigbee thermostat in your house and sending your rsa keys to the pentagon? Who says yo home wifi point isn't acting as a decrypting proxy?
We cant tell, and that's the point. There is no way to ever observe these levels complexity and verify security and we don't admit it.
We will never know if the code we are running on our various devices is doing anything extra or not, and so rationally, we should never trust it at all.
Not to say all sec is pointless, you don't want to be low hanging fruit, but above 'insta-pwn' levels of stupid there isn't much more available, even if you're told there is and we keep pretending like we have any control over what's going on anymore...
But regardless of that point, your other argument feels to me like a discussion against the problems of mono-culture: we should all endeavor to have diversity of implementation, if possible. The more we can work towards federated standards and the ability to quickly pivot when someone loses our trust, the more capable we are of defeating attempts to undermine that trust. If we only have 1 implementation of signal and everyone uses it, then all an "evil" party has to do is find flaws in that 1 implementation. If we have 2 implementations, then some users are protected. If we have 1,000 implementations, and they all inter-communicate, then we have some hope that only some users are affected by each compromise. I'm digging matrix.org as a federated protocol, and I'm hoping that it takes root because it has many clients; an open, federated protocol; and the ability for me to run my own server.
I would advocate that even though we're relatively mono-culture on linux, supporting it at least gives linux access to the source code which would allow other implementations (anyone else keeping a close eye on Redox [1]? I know I am!). Support open protocols! Support federated protocols! I'll advocate that signal is a great, easy-to-use system for secure communication, and that the ideas of Signal are percolating elsewhere (see "olm" [2] the implementation of Signal's crypto protocol for matrix). But I would like to see stabilization in Signal leading to federation.
Basically we are in Intelligence vs Counter Intelligence game with the state.
You suspect your phone or device is listening? I know that Facebook is listening/monitoring, so I let it hear. Yes, I did go to school in Zimbabwe and have my Zimbabwian friends confirm it, and I did visit it look the GPS data in the pictures show it.
The data that facebook has about me is worthless shit in disguise as marvelous worthy data, but they do sell it well, if everyone did this, it would be obvious their data is not worth the ads they sell, facebook would crumble like a stomped on paper plane.
* The "everything is fucked and will never get better" group, which I'd put your message into
* The "everything is fucked but you're not being targetted by Mossad" group - at least these people do threat modelling.
* People who are actively helping journalists in dangerous areas (see my first point)
I agree with lots of things in your message but I don't think it's helpful. Would you say we should drop back to HTTP because there are lots of ways to break HTTPS?
There are people doing fantastic work even on closed platforms like Android and iOS. People are looking in detail at what's running on it - mostly thanks to the jailbreaking and rooting communities. Everything will be OK, it's just going to take a lot longer than you'd like it to.
However, I despair that a secure by design internet is impossible in this civilization, because it will be designed in an environment that includes "stakeholders" like Google, Facebook and the NSA via NIST. The only thing that you can do, beyond waiting for a white knight service, is button down your end, try to convince the other end to do the same, and use niche and custom built tools.
There is no secure future for the internet as we know it, or as it might come to be in the current civilization.
> But, HN, I don't know why WE aren't admitting this to ourselves or why we defend such obvious ruses.
What exactly makes Signal an obvious ruse? Many of us don't admit that evading surveillance is impossible because we work full time in commercial surveillance. This is the currently dominant business model of the technology industry. Many of us have also worked in defense / government. At the very least, the fact that we have a non-commercial FOSS alternative to data-collection-traps, which is gaining traction, is fantastic.
> Well, maybe some of you have signal stock I guess.
Signal is run by a non-profit.
You just sound like you're spreading FUD.
I strongly disagree, Skype has always been a black box. The usability of Signal's crypto is a lot better than it has ever been for Jabber.
> I can understand the reasons for not supporting federation, but I disagree.
Yet you don't address any of the problems with federation.
> What Open Whisper Systems and Wire need to do is open source the server components of their solutions, and try to remove the reliance on servers as much as possible.
I saw a BBC documentary in the mid-early 2000s (sorry, can't cite it right now) about law enforcement and intel having a really tough time with suspects using Skype, only being able to collect metadata and not call content due to its split routing protocols.
Now, there's nothing to say the whole service wasn't backdoored at some point, but it appeared to be a real concern, at least to LE. A few security audits at the time also gave it a very positive report (ditto for citation). In the post-MS sale era, of course there's zero trust. Prior to that though, things seemed different.
The encryption is audited, but not yet enabled by default, as there are still some rough edges. But the apps have tremendously improved over the last few weeks alone and I am very happy with it.
Signal uses Google Play Services to notify me that I have an incoming message from Signal. The Signal app is then woken up and the signal app then retrieves my (encrypted) message. So, therefore, the only thing Google knows is that I received a Signal message, what time and if I have location services on, where I was at the time, yes?
On iOS, how is this any different? If I get a notification, iOS knows I got a notification from signal, when and where i was at if Location is turned on.
What am I missing?
Note: I _don't_ like that either system has that much meta data about my conversations available to them, but I don't see how one is better than the other, here.
> Signal uses Google Play Services to notify me that I have an incoming message from Signal.
More importantly:
a. That dependency, along with other "restrictions", sets an artificially high barrier to actually using the product independently. This is presumably so that they can maintain the pretence of being "open source".
b. Keep track of application downloads and whatever else Google provides to developers.
Moreover, as the paper that someone has linked elsewhere says, if you are allowing Google services in your app (Google Cloud Messaging, to be exact), you're at the mercy of anyone with control of it. A relatively trivial attack via GCM, as the paper hints, would involve simply replacing your application with a backdoored version, and you'd be none the wiser. It is a massive attack surface that just cannot be ignored.
Considering that Signal compiles code from Google into their app, there’s an actual issue there: the Google code could just intercept and take control of any of the messages. And there’s a lot of code from Google in there that no one has audited yet.
The Signal Server is open source, as far as I know.
Yes, except for the voice call component.
The friend had a crash shortly after opening it on iOS, but it went OK after that.
You can't paste or drag in images directly on any client, as far as I can tell.
The "desktop app" is a Chrome app (not even Electron). Not loving that.
There were some hiccups with contact syncing.
It decided it should be responsible for alerting me to receiving ordinary phone calls (!?) on my iPhone, for some reason, which was annoying.
We abandoned the experiment pretty quickly :-(
[EDIT] it also lacked nice-to-haves one might be used to from other messengers, like auto-emojification.
That said, based on OWS' writeup on the subpoena they received[1], the only user metadata they collect are the user's phone number(or a hash of it? for identification), that user's last connection date, and the dat etheir account was created.
[1] https://whispersystems.org/bigbrother/eastern-virginia-grand...
Actually, Jabber with OTR is pretty solid. If need be, you can use throwaway addresses too.
> I can understand the reasons for not supporting federation, but I disagree.
I disagree and can't understand the reasons, which however I suspect to be rather shortsighted. Just imagine if email had not been what came to be called a federated system.
I don't know the real reason for Signal getting rid of SMS encryption but it's the only feature I'm interested in. I can get glorified internet messaging anywhere, but OTR encryption over SMS is a difficult problem due to the inability to conduct handshakes. We should not throw this work away.
WhatsApp at least has end to end encryption- though that alone isn't enough, but it is not open source and is owned by Facebook. By default, it shares your number and your contacts' numbers with Facebook.
Neither Telegram nor WhatsApp are viable alternatives to anyone interested in privacy.
Why? I'm not trying to nitpick, I just don't know much on the subject. Not being open source doesn't really concern me nor the fact that my number is known by Facebook. My telecom company knows it, my mother knows it and all my friends know it + also all the companies know it who are used by my friends.
https://core.telegram.org/mtproto https://telegram.org/apps#source-code
Are you suggesting that the application under discussion here is a viable alternative? If so, how?
I'm honestly asking here--I don't have the knowledge that many in this community do about the exact risk of Signal requiring Google Play Services for example. If Signal isn't the answer, what should I and others use who require a usable, reasonably accessible to non-tech-professionals solution?
I understand all the concerns people have about Signal and I share most of them. But these discussions really are for people who want to build something better, not for people who look for something they can use now.
previous discussion: https://news.ycombinator.com/item?id=12864429
There were also forks of Signal which fixed the privacy issues, however Moxie Marlinspike (the founder of Open Whisper Systems) ordered them to cease and desist.
"Tox is by no means complete. You may encounter bugs ranging from simple visual defects to segfaults on file shares. We cannot guarantee what works today will work tomorrow; Tox is an alpha program and code changes daily. Certain commits may break existing APIs, and we strive to give proper advanced warning to all client developers, etc. when such changes will be made. Additionally, Tox has not yet received a full security audit. While we believe Tox is secure against attackers who want to decrypt your messages, you may wish to use a more established solution if you are in a life-or-death situation."
If you're in a life-or-death situation, I think you really ought to be doing some intensive research into secure communications to find the solution that will work best for you.
Would you be kind enough to provide links? I can't find any information about this claim via Google, and Signal is distributed under the GPLv3, which grants rights to fork and modify it: https://github.com/WhisperSystems/Signal-Android
tl;dr: You can fork the Signal code if you want, but if you do, Moxie Marlinspike asks you to change the app name and run your own servers. The server source code appears to be available at https://github.com/WhisperSystems/Signal-Server, but I've heard it doesn't include the voice component.
So, for example, if you think that Signal ought to support a feature like iMessage's "Invisible Ink" (https://mic.com/articles/146347/i-os-10-s-invisible-ink-feat...), which Moxie has specifically refused to support (https://github.com/WhisperSystems/Signal-Android/issues/5103), then you can't just fork the client, implement it yourself, and use the new client normally, because you'd no longer be able to talk to regular Signal client if I understand correctly. I mean, even if you figured out a way for two clients to tell each other whether or not the feature was available.
So Signal is open source, but not in a way that's useful if you want to change something.
I don't want to discourage people from using Signal. It's a great app. But I thought this was worth pointing out, assuming the LibreSignal is representative of what will happen if people want to make changes to their client.
Especially if the original client is under an open source license.
Nearly everyone I know uses WhatsApp. This change made the platform much more secure for everyone. It's on by default and works transparently. Since then, at least one government was unable to compel WhatsApp to produce messages² from users under investigation.
I also have Signal installed but nobody I know uses it so its utility is diminished. I told some friends about Signal; they installed the app but won't use it because they can't message anyone except me. The only times people talked to me via Signal was during the temporary WhatsApp blocks ordered by my country's government.
¹ https://whispersystems.org/blog/whatsapp-complete/ ² http://www.forbes.com/sites/parmyolson/2016/05/03/whatsapp-f...
With the wire desktop app you can take steps to anonymize your connection to their server, although on a mobile device it's probably roughly equivalent to Signal.
Also, here is a handy chart that compares the differences between these two services (and other similar competitors). https://wire.com/privacy/
They have broken voice encryption, and leak enough data to reconstruct the audio of your calls. They leak tons of plaintext directly back to themselves, like GIF searches, and rolled their own messaging crypto that experts say is broken.
They have been caught lying about what kind of encryption they provide, they lied about being open source for years, they lied about being based in switzerland. From what I can tell, the only people promoting Wire after all that are usually on Wire's marketing team.
I have been using XMPP since 2000/2001. My current address is nine years old (and I control the server). I have a choice of clients on every platform that I use. All my contacts have the same set of choices regarding provider, accounts, and clients. As a bonus, not just my human contacts but also my infrastructure uses it for messaging and monitoring, so I can literally control some of my servers from my XMPP clients.
There must have been at least thirty major IM "solutions" going in and out of fashion during these 16 years. Individually, each might have been somehow "more convenient", but if start counting the cumulative migration effort, I'm not sure the convenience argument holds much water.
¹ I used it in anger once myself, initiated by one of my contacts. It was an interesting experience.
Also, how do you get all your contacts to use XMPP and your server?
It depends on your threat model, like other alternatives.
I have never initiated an OTR session myself, but I have received one from a contact in anger (whistleblowing).
> Also, how do you get all your contacts to use XMPP
In my case, I have been using XMPP for the last sixteen years, so my contacts have "grown organically", to use an en vogue marketing term.
It appears that Mac computers come with an XMPP client preinstalled (and possibly pre-configured?) Linux, the same. Android, there are a number of clients available. Windows, I think there is Gajim, ...
As far as a stereotypical common user is concerned, they are quite happy to install whatever applications their peers are using, which is how they end up with so much cruft on their computers, phones, etc. :-)
> and your server?
Nobody needs to use my server. It is like email, you can use whichever provider you like.
I hope this answers your questions!
Convince them :-) Same as with any other.
Don't want to invest my time into something that will eventually sell out and do that opposite of what they stand for today.
And what do you think the gentleman behind Signal is out there for?
His modus operandi:
* Start a company, call it something catchy, like Whisper Systems.
* Get media coverage and some users.
* Sell to Twitter
* Start a company, call it something catchy, like Open Whisper Systems.
* Get media coverage and some users.
* ...
Start to see a pattern? :-)
https://www.reddit.com/r/privacytoolsIO/comments/57n8ee/inst...
As I see it, there's some sort of trade off for all solutions for private instant messaging right now. Wire comes close to a good solution. The biggest problem for me is that the official Android client is quite buggy, UI wise...
You can set up an SMS gateway number just for this purpose, but you shouldn't need such workarounds.
That's true, although those of us with unlocked phones can purchase "throwaway" SIM cards with distinct phone-numbers fairly easily with cash, use the number for secure communications only, throw the card away, and then go back to our public lives.
You gotta burn the phone.
So other than full-on burner smartphones (ie: throw away $600 every time you need to do something privately), what's a reasonable heuristic for conducting private business? Maybe collectively owned or rented burner phones so that the metadata collector only ever knows, "Someone rented this device for encrypted communications" rather than who in specific is communicating with whom?
You need to do a threat analysis.
I did not immediately find any good introductory resources via a quick Google search, but try it yourself. Very very briefly, it involves identifying the threats and their possible consequences, then working on either removing the former or minimising the latter.
Be aware that this is not merely a technological process. It is primarily a social one.
I made us switch to WhatsApp instead as I think the usability/privacy balance was better (for our use case).
Signal for Android was really amazing, and the switch made me think this could be one reason why so many people seem to speak both highly and poorly of Signal. The iPhone app just unfortunately seems to be way behind the Android app.
Not sure why they have prioritized development in that way.
The programmer working on the iOS version left early this year. If you look it was pretty stagnant for awhile with him, only really getting bugfixes. Now they have a new maintainer that's been playing catchup and things really only started to get rolling in the past couple months.
See: https://github.com/WhisperSystems/Signal-iOS/graphs/contribu...
Still havent figured out why my friend cant download Signal from Apple App Store.
At the very least Signal requires iOS 8.0 or later.
Having the NYTimes advocate for crypto so clearly and to such a large audience will make a real and tangible difference to users - more than can be said for the years of online nitpicking by experts.
That this is a deficiency worthy of mention reveals just how different the average person's values about what a messaging app should do are from mine.
Missing feature #2: only the Android app can be paired with Signal Desktop; the iOS app is left out. What's up with that?
And iOS for a while now! https://github.com/WhisperSystems/Signal-iOS/pull/886
The little I've used it, I found it pleasant and effective. But it almost seems like there is a campaign to ignore Wire; nearly every article written about Signal and alternatives fails to even mention Wire.
They have done a bunch of shady things:
1. They lied about having end-to-end encryption in their app: http://www.pcworld.com/article/2855745/new-communications-ap...
2. They lied about being open source for years.
3. They lied about being based in switzerland.
They also have serious problems with their app:
1. The "encrypted" calls leak enough information to be able to reconstruct the audio.
2. Many features in the app, like GIF search, transmit plaintext directly back to Wire.
3. They rolled their own crypto, and experts disapprove of the choices they made.
Journalists who write articles like this and don't mention Wire are doing their job. They've consulted with experts and aren't spreading misinformation.
That was before I joined but that got fixed in 24 hours. Not sure how the incorrect claim made it live in the first place.
> 2. They lied about being open source for years.
Wire open sourced it's crypto protocol in March 2016. It never claimed to be open source before that. It further open sourced it client apps in July 2016 and will open source server some time in 2017.
> 3. They lied about being based in switzerland.
Citation needed. Wire is registered and headquartered in Switzerland with an office in Zug.
> 3. They rolled their own crypto, and experts disapprove of the choices they made.
Link?
GIF searches are obviously going to use a 3rd party service, and nobody should expect some kind of anonymous encrypted channel for GIF searches. That's ridiculous.
I've not seen any lying about being open source. They haven't released every piece of code, but I don't recall them ever claiming they did. https://github.com/wireapp
I've never seen any crypto experts who have audited Wire and said there's anything wrong with their choices, and you supplied no links.
Between all the options, including Signal, I personally think Wire is best, and nothing you've provided has any reason to change that.
By proxying the encrypted request through another server, signal never sees the content of the request and giphy never gets the identity of the requester. I'm not sure that this is strictly necessary, but it certainly increases my confidence that the signal team are serious about their work.
GIF searches aren't being transmitted to a third party service, they're being transmitted directly to Wire in plaintext: https://github.com/wireapp/wire-android-sync-engine/blob/4d5...
There's tons of stuff like that which leaks in the app. They store your entire contact list server-side, your plaintext group membership, group info like plaintext group name and plaintext group avatar, etc etc.
> I've not seen any lying about being open source. They haven't released every piece of code, but I don't recall them ever claiming they did.
Since their launch several years ago, they've had a "feature" matrix on their website that lists Wire as being open source (and their competitors as not being open source). That was long before their recent "open source" announcement (which still isn't even fully open source). When pressed, they said it was because they used some open source libraries. That's really shady.
> I've never seen any crypto experts who have audited Wire and said there's anything wrong with their choices, and you supplied no links.
Here's one example I saw recently:
https://www.cs.jhu.edu/~cwright/oakland08.pdf
They're vulnerable:
https://github.com/wireapp/wire-audio-video-signaling/blob/c...
Even worse, they also apparently include plaintext RTP headers with audio level information in them.
One has to remember that Signal also stores some social graph data, which is equally problematic.
I can’t reocmmend either.
One that, to my knowledge has not been mentioned yet, but which would appear to meet some common measure of functionality versus convenience expressed here, is XMPP messaging application Conversations (https://conversations.im/).
I am not going to give it my personal recommendation because having tested it, I did not like a number of design decisions the developers have made, and I did not like their overall vision for the app. With that said, it's horses for courses.
On the end to end encryption front (all the rage these days, eh?), it appears that the Conversations devs have taken Signal's protocol and _done it right_. That means, they actually specced it (https://conversations.im/omemo/) and had it audited (https://conversations.im/omemo/audit.pdf), along with a couple important improvements such as eliminating the requirement for a trusted server or Google Play, which greatly reduces the attack surface.
Again, I personally do not like Conversations and I'm not going to use it myself--that's a personal preference thing, but kudos to the devs for doing a professional job, especially while everyone else are busy selling snake oil.
I say, go give Conversations a try, it may be the thing you were looking for.
It seems very counter intuitive,. Worried about privacy & security of your messages? Oh firstly you need to trust all your personal contact info to us. Yes they say they don't use it off of the phone, but it's asked for and that's based on trust.
On iPhone it requires access to your contact list. Surely it could run without this? Snapchat for example makes it easy to add friends in person, by scanning a code on one phone from another. How is sending unencrypted text messages announcing your social graph the only way to use the app.
Why is the app asking for so much permissions trust itself?
Second, Signal only stores account creation date and I believe account deletion, or some other super-basic info like that. But that's it. Meanwhile, not only does Whatsapp collect much more metadata, including the groups of which you're part, but it has also started sharing that data with Facebook recently.
I'm not saying you should stop using Whatsapp, though. I still think it's a better alternative to iMessage/Hangouts/Skype/Telegram. But at the same time you should slowly transition your most important contacts to Signal, too. One nice extra feature Signal has over Whatsapp now is Snapchat-like disappearing messages, so at least you may be able to convince some friends with that.
The suggestion that the motivation for this article is profit for the NYT or Moxie is quite destructive.
No, that's literally how it works. Media need to sell copy (clicks these days) and companies need to get coverage. And that's perfectly OK if companies are acting ethically and journalists and editors are doing due diligence.
The person that you mention has good connections in the media and uses them to self-promote and promote the tat he sells.
It's free.
And normally one would associate such vehement and repetitive insistence on counter-factuals with trolling
You misunderstand. He is running a company, what do you think their exit strategy is? You may want to look at his previous company and "red phone", I think was his product called.
> And normally one would associate such vehement and repetitive insistence on counter-factuals with trolling
I am sorry that you do not like to hear this.
https://blog.decred.org/2016/12/07/zkc-Secure-Communications...
"zkc is a blending of what we consider to be the best parts of both of these projects, Signal and Pond" "The UI is text-based and emulates the appearance of irssi, in order to keep UI-related complexity low and avoid large GUI toolkits as a dependency." "intended to provide the highest level of communications security balanced with minimal complexity in its code, configuration and usage."
Regardless of the framing of the article, many people likely read this and thought, "yes, it would be nice to be confident my messaging is private even from mass government surveillance."
This does not mean they are drug dealers. It means that they have concluded wide-dragnet surveillance programs are worth opting out of, especially if it's very easy to do so.
It means for me, but I fail to see why it is bad. Even direct "not your business" does not prove any guilt. It is okay to hide, we don't have to be open book.
Signal is a joke if your adversary is NSA and its likes. You cant run Signal unless you give up who you are, and that you are using it, and its not very difficult to analyze _when_ you receiveor send a message due to the Signal requiring google messaging system.
Signal should just really rename itself to "Google Signal, no really we are not evil for certain."
Your last sentence is extremely unfair to Signal and dramatically underrates the privacy it provides to ordinary people. It's dangerous to suggest that because it requires a phone number and lives on an app store it provides no useful protection at all, because that implies it's no better than e.g. WhatsApp when in fact it has a much better featureset.
Almost everybody might be in that situation, because the NSA is not the only group that has access to the data they collect. They call it "parallel construction", where the NSA's "customers" like the DEA simply have to fill out a form[1] to get surveillance data, and promise to lie about the source in court.
[1] https://www.techdirt.com/articles/20140203/11143926078/paral...
In fact, its worse than cleartext SMS, when you use Signal you are a target, when you use cleartext SMS, you can still hide among the noise.
What messaging system would your recommend instead? Riot? Tox? Last I checked, neither were nearly as polished and feature-complete as Signal. In my use case, unless it is good enough to become a daily driver, many people won't even bother with it. What good is a messaging system that nobody else uses?
Telegram, cleartext SMS, email.
Normal people do not send anonymous or secure messages, but if you need and want to, then you cant just install an app and be done with it, you have to first find and install I2P which is not traceable to you (good luck, first get a degree in information security and become Linux guru), then join an I2P only IRC channel and begin messaging with your group of people about plan to watch football and drink beer, after you had the secret communication with bitmessage over I2P.
Why make it so easy for them?
The fact that the guy behind it is hyping it via the New York Times, a generalist publication, instead of validating the thing through professional cryptographers (which he isn't) and recognised privacy champions such as the EFF is very telling.
The thing has not been properly validated or verified (for a start, because there is no design document to validate against, and no published goals to verify against), it uses an ad-hoc encryption scheme from a non-cryptographer, it is not open source (see F-Droid discussion why it's not there), it uses hardwired servers controlled by a party or parties which are not known to be trustworthy, and apparently it requires Google Play services, which nobody who is truly concerned about their privacy is going to use in the first place (and definitely one should not).
From the way this is going, it is becoming clearer by the day that this is just another start-up, their target market are unsophisticated but paranoid users and hipsters with no real need for privacy but who think they should make some kind of statement. Their plan is to hype it up (e.g., via the NYT), get enough users, then get bought by one of the so-called "social media" players. It is more attractive to them than Telegram because the latter is run by a Russian, which to the American public sounds sinister (Mr Brin and countless other great scientists and innovators notwithstanding), and their servers are probably based in Germany, which is a bit more of a problem since there are (still) some proper privacy laws over there, and which would cause some headaches to the acquiring party. Besides which, there is a good chance that their current investors come from those "social media", or are the usual Silicon Valley VC crowd, so things stay between friends, as it were.
So, in brief:
* If you want a new Skype, go for it.
* If you care about the privacy of your communications, you should avoid it.
* If you need to keep your comms private, you must avoid it.
Anyone disagrees? Feel free to reply and tell me why!
> The fact that the guy behind it is hyping it via the New York Times, a generalist publication, instead of validating the thing through professional cryptographers (which he isn't) and recognised privacy champions such as the EFF is very telling.
Cryptographer Matthew Green on Signal's crypto and code quality (it was called RedPhone/TextSecure at the time of this writing): https://blog.cryptographyengineering.com/2013/03/09/here-com...
Version 1.0 of EFF's Secure Messaging Scorecard gave Signal 7/7: https://www.eff.org/node/82654.
> The thing has not been properly validated or verified (for a start, because there is no design document to validate against, and no published goals to verify against)
Signal has been analyzed, with favorable results, by academic researchers at least twice:
- https://eprint.iacr.org/2014/904.pdf - https://eprint.iacr.org/2016/1013.pdf
> it uses an ad-hoc encryption scheme from a non-cryptographer
Moxie Marlinspike and Trevor Perrin probably wouldn't call themselves "cryptographers," but almost anybody in the field would agree that they are experts on applied cryptography.
I'm sorry that you get that impression, but I do appreciate your input.
> Cryptographer Matthew Green on Signal's crypto and code quality (it was called RedPhone/TextSecure at the time of this writing)
That's the application that they sold to Twitter, not the one being talked about here. I do not know how different the code bases are.
It is also around that time that the app had a gaping, amateurish hole in that it was simply leaking everything via logcat. And what does the guy do? Instead of addressing the issue like a professional, he goes on a complete tangent rubbishing F-Droid (https://github.com/WhisperSystems/Signal-Android/issues/53) and then making rather poor excuses as to why you should get your application from the Google store and not from anywhere else.
Excuses which by the way, have been evolving over time. I think he eventually admitted that he wants to keep track of how many users are using it (handy to show to your potential buyers).
He also has a history of lying, such as when he used fake WHOIS details to run his "Google anonymiser" thing. And of course, when he was shut down by the registrar, as you do when someone has given you false details, what did he do? He went to the press to whine about the registrar! After he entered a contract in bad faith, something which happens to be a prosecutable offence. That's the sort of person we are talking about here. I hope you will understand if his word does not exactly fill me with confidence.
> https://www.eff.org/node/82654.
That page starts with: "This is version 1.0 of our scorecard; it is out of date, and is preserved here for purely historical reasons."
And continues with: "the results in the scorecard below should not be read as endorsements of individual tools or guarantees of their security"
> Signal has been analyzed, with favorable results, by academic researchers at least twice:
Yes, I am aware of those. And that is not what validation and verification is which, as I said, in the absence of publicly available design documents, is impossible to do independently. The guy is trying to make it look like he's selling a "secure" communication platform, but if you presented that to a defence contractor (which I have some experience with) you would be laughed out of the building. Proper security is not done like this at all. For a start, you actually define your goals, i.e., what you intend to secure, against what threats, etc., etc. If you can show me a paper with that information I would be grateful.
Notably, you may have noticed that those papers, like Green's, are a protocol analysis, not an analysis of the entire solution. In that respect, you're back to the previous situation: the protocol might be ultra-secure, but if you're still leaking your plaintext on a different channel...
> Moxie Marlinspike and [...] probably wouldn't call themselves "cryptographers,"
At the risk of sounding elitist, what is his academic background? (I elided the other person because I do not know who he is).
> but almost anybody in the field would agree that they are experts on applied cryptography.
What do you base that conjecture on?
I really don't see why someone should be on my shitlist for lying to godaddy dot com or whatever giant registrar unless you consider fudging identifying details about something that really doesn't matter, especially considering he was very openly associated with the project, some sort of horrible moral offense. I especially find your taking massive umbridge with fudging personal information baffling given how privacy-minded you otherwise seem.
>At the risk of sounding elitist, what is his academic background? (I elided the other person because I do not know who he is).
Combined with the above, the way you're hand-waving away the other of the two original developers of the protocol really just makes it seem like the position you've taken against Signal is mostly predicated on some sort of grudge against Marlinspike himself. Yes, trashing F-Droid was not a great thing to do and you might see him as someone with a strong penchant for self-promotion, but the way you keep on tying your criticisms to Marlinspike personally really muddles your case. For example, you object to him promoting Signal in a New York Times piece saying it is a generalist publication and posit he's just trying to drum up attention so he can find a buyer, which may or may not be true, but isn't one of the most important goals of a secure messaging application to get people to actually use it and to achieve widespread adoption? The main lesson I've learned from GPG mail is that a perfectly private means of communication is worth very little if I can't actually convince anyone to use it with me.
I think I can see where you are coming from. You seem to compare this with, say, opening a GMail account under an alias, if I understand correctly.
However, holding domain names and, at the time, SSL certificates requires a different sort of accountability. I can elaborate on that if you wish, but I trust it won't be necessary.
> especially considering he was very openly associated with the project,
In the same way that Mr platinumrad or Ms at612 are associated with this discussion? By the use of an alias?
> some sort of horrible moral offense.
Yes. And please note he did not just lie to the registrar. When he got caught, he went and whined to some journo who published a piece criticising the registrar without bothering to contrast the information first. It all being presented as if it was the registrar in the wrong, when they were following the rules, which are there to protect the public in the first place. This coming from some bloke who was saying "don't trust Google, trust me. Because."
> I especially find your taking massive umbridge with fudging personal information baffling given how privacy-minded you otherwise seem.
I value my privacy. At the same time, when I enter a contract, I do so in good faith and of course part of it is letting the other party know who I am.
> really just makes it seem like the position you've taken against Signal is mostly predicated on some sort of grudge against Marlinspike himself.
Yes, you are correct. My apologies if that wasn't clear. I question the ethics, motivation, and competence of this one individual, who happens to be closely associated with said project.
> Yes, trashing F-Droid was not a great thing to do
To put it mildly. On an incidental note and more generally, have you ever seen him do a mea culpa?
> [but] isn't one of the most important goals of a secure messaging application to get people to actually use it and to achieve widespread adoption?
I do not know. I would guess not (based on defence experience). But the main point is that him saying "oh sure, it's secure" does not make it secure. He seems to be taking advantage of the public's inherent credulity and lack of awareness of what "security" actually means and involves. We have gone through this discussion already, so for an example of what I consider a better developed and correctly presented security solution, please see the Conversations IM application.
> The main lesson I've learned from GPG mail is that a perfectly private means of communication is worth very little if I can't actually convince anyone to use it with me.
This is a different, and long discussion, but it is probable that the reason why you are seeing that is the other party having mentally (or formally) done a cost/benefit analysis and deciding that their information is not of such value to justify the extra effort to protect it. Rightly or wrongly.
This isn't just unique to Android: there are multiple ongoing efforts at the moment in the Linux world to lessen frustrations with distribution repositories. Snappy, Flatpak, and AppImage intend to unify application deployment and allow users to install applications from anywhere. In most cases, this could mean pulling directly from the application developer themselves. GNOME and KDE will likely encourage this.
I know some Firefox developers who have grouched at the delay between official releases and when distributions finally deploy them, so this problem isn't exclusive to desktop environment developers.
Back to Android: Moxie had a point when he claimed that Android is more privileged to have a system that provides package verification back to the original developer. It doesn't matter where you get an APK from: the developer's website, Google Play, APKMirror, or Bittorrent. If you have the developer's public signing key, you can verify the authenticity of the APK.
F-Droid represented a serious step backwards in Android security, back when they used to self-sign APKs. It wasn't possible any longer to cut out the distributor from the chain of trust. Fortunately, they reacted to Moxie's criticisms, and F-Droid now retains the original package signature when the build can be reproduced.
From a developer perspective however, encouraging or even tolerating unofficial installation channels for secure communication software is bad. If vulnerable users are in-contact with non-vulnerable users, they unknowingly put both parties at risk. If the ecosystem evolves to the point where this is common, the whole system is insecure.
What Android desperately needs is a high-quality, non-profit, privacy-friendly, charity- and grant-driven app store. It must entice open-source app developers. It cannot do self-builds, except for reproducibility. It needs crash-reporting, analytics, usage metrics, device-specific builds, localization options, and more. It requires dead-simple tools for command-line deploying.
Until then, in my opinion, F-Droid will never be accepted by app developers. F-Droid is for users only. Not for the same purposes, either: for the cautious user, F-Droid mainly shines as a locally-setup repo for self-deployed apps.
P.S.: Perrin & Moxie recently began documenting Signal Protocol: https://whispersystems.org/docs/
What is your threat model?
Huh?
https://github.com/WhisperSystems/Signal-Android
I'd even argue it's free software - the team has managed to create some confusion about distributing modified binaries - with regards to using the servers Signal operates -- but have clarified that it is indeed ok to build your own binary from the source they provide, and use their servers.
I'm not quite convinced about their argument for official app store distribution and updates, but I can understand the argument.
> it requires Google Play services
I'm fairly sure the iOS client doesn't depend on Google Play Services. Sticking with an app store does require trust in the provider though.
Whisper System have made some fairly clear choices, and while it's perfectly fine to disagree, I think it would be best to avoid FUD.
It certainly strikes me as one of the better options for pragmatic secure messaging, that allows for a fairly narrow and reasonable set of threats (Google/Apple/Microsoft (possibly more than one of each, depending on your platform), Whisper Systems themselves, probably most state actors).
The other reasonable option I'm aware of (that make slightly different trade-offs), is ChatSecure/zom.im (where zom.im is a "friendly" fork of ChatSecure).
Terminology. What you call free software I call open source. As you go on to mention, you can see the source but not use it in any meaningful way. In particular:
> but have clarified that it is indeed ok to build your own binary from the source they provide,
Exactly. Your own binary. From their source.
Build your own binary for someone else, and it's "malware", as the guy had the nerve to call F-Droid in that bug report (here: https://github.com/WhisperSystems/Signal-Android/issues/53). That sort of bad faith, coming from a known liar (see my other reply) is what I really cannot condone.
> and use their servers.
Yeah, similarly. Use a source other than theirs or servers other than theirs and they start whingeing.
That is not open source.
> I'm not quite convinced about their argument for official app store distribution and updates,
Possibly because every time it's a different excuse?
> but I can understand the argument.
Yes, so can I: they want to control the platform so that it is their users, so that they can sell it to someone else, like they did last time.
And I would be perfectly fine with that, if it wasn't done via lies, deception, and denigrating third parties, particularly the chaps at F-Droid who at least have the decency of using their real names (not to mention not seeing you as the product).
> Sticking with an app store does require trust in the provider though.
Agreed. How high is Google in your "trusted" list? Yes, I'm picking on Google because it's a bit of an easier target than Apple, but still.
> I think it would be best to avoid FUD.
I agree, and that's precisely why I feel the need to speak up. I challenge the honesty not of their enterprise (which is no different from that of Skype, Whatsapp, or any other player) but of the way they are pursuing their goal. See above.
> It certainly strikes me as one of the better options for pragmatic secure messaging,
I don't know. As mentioned elsewhere, XMPP meets all my requirements and is not vendor-dependent. But the availability of options depends on each user's definition of things like "pragmatic" and "secure" (and even "messaging" for that matter!)
From seeing what's out there though, it appears that modern versions of Whatsapp (which I don't use, I'm FOSS-only) offer essentially the same capabilities as this application though, including end-to-end encryption. And of course, essentially the same disadvantages. I could be mistaken here though.
> that allows for a fairly narrow and reasonable set of threats (Google/Apple/Microsoft (possibly more than one of each, depending on your platform), Whisper Systems themselves, probably most state actors).
I guess it also depends on each user's definition of "fairly narrow and reasonable". :-)
As for your other comments - you may run your own server infrastructure from same or derived sourced, your own derived clients, distribute binaries etc - but you can't dilute the brand. Similar with Debian cloud images for example.
I'm not sure how that's "not FOSS".
That sounds like a feature more than a deficiency.
There are better ways to give feedback than just saying a free app is "crap"
Telegram does so by default, you have to opt in to keep messages private from the server.
You also see a lot of people criticizing the design of the secure Telegram protocol and praising the Signal protocol. There were some stories about governments actively compromising Telegram's security. There haven't been any about Signal.
So if you are worried about privacy more than UI and rich functionality, the choice seems clear enough.
You can use secret chats, those messages are not stored on the company server.
The unencrypted messages are certainly not secure, and it's disingenuous of Telegram to market itself as a secure system without being really clear about the limitations.
For messenger to gain a MASS of users it has to be 'enter sms-code and go chat'.
For messenger to be SECURE it has to be 'install password manager, set passcode, use 2-factor, use e2e, use self-destruct, always compare keys'. No one will enjoy that. But if you need, you just have it in your regular sexy messenger, not in another ugly alien app that no one knows about, no one has installed, no one's ready to go through all of it.
I think telegram guys got it just right.
[1] https://telegram.org/blog/15million-reutersAnd I would be really interested to know why people are downvoting a perfectly reasonable question.
[Edit] - "Use their proprietary client and trust them on their pinky promise" was factually wrong.
But, they still expect me to trust the signed binary they send through the App store right? How is that anyway non-proprietary just because there is a Git repo somewhere that may or may not be the same code running on your phone? Can I run a client from the Git repo and still use all of their infrastructure?
There are valid criticisms of Signal (primarily around the use of the Google Play Services Framework), but your comment seems to be jumping to a lot of conclusions without any research.
Until I'm able to do that, it is still their "pinky promise".
Yes. You can.
They describe how in the very repo I linked. Your ardent unwillingness to spend the 30-45 seconds it would take to find this out before spouting unwarranted false criticism is quite strange. Do you have some personal issue with OWS?
I really didn't mean to be defending OWS here - I'd much rather see Signal leveraging non-Google APIs in some way and provided via F-Droid (though I have read their arguments against that w.r.t. performance) but I'm astounded at the wilful ignorance here.
If you're genuinely interested in promoting secure messaging, a desire to get your facts straight and answer your own questions instead of assuming the negative should be step 1. Otherwise, you're needlessly steering people away from a tool that could practically improve their privacy.
> Yes. You can.
The thing is, lucideer, the "restrictions" on the use of the source code are engineered to raise the barrier to independent use, notably by preventing or discouraging redistribution. This means that only those who are able and willing to compile Android source can run their own binaries. Everyone else has to go with the binaries they distribute which, as the other poster has correctly argued, cannot be independently verified.
> Do you have some personal issue with OWS?
I do not know about him. But I do. Please read on.
> and provided via F-Droid (though I have read their arguments against that w.r.t. performance)
Oh, so it's "performance" this time? It's not something about "updates" like last time¹, or "features", or "metrics"?
Do you really not think, if you go through the discussions, that there's just too many excuses? Does it make sense to you? Do you not get the feeling someone's got something to hide, if you would pardon the pun? :-)
But I tell you what really got in my tits, it was this message: (https://github.com/WhisperSystems/Signal-Android/issues/53#i...)
"Please do not install software from F-Droid. It is an unverified build, exceptionally out of date, and should be considered malware."
You know what? I fucking trust F-Droid. And I for one I am very grateful to everyone who collaborate to make that happen and stand firm in their commitment to open source, and especially to Ciaran, the founder, who gives so much to the community in spite of very challenging family issues (which are publicly known). Top bloke he is.
And then you get some lying, incompetent, manipulative², and possibly delusional individual accuse them of distributing malware. That is seriously not cool.
For those of you unaware, this is the person we are talking about (I suggest you read the comments too): http://www.gandibar.net/post/2010/04/07/The-googlesharingnet...
¹ Cooperative and competent (or at least willing) open source developers can set it up so that F-Droid auto-builds every time you tag a new release. ² And I say this because I'm sure someone will correctly argue that he did not call F-Droid itself malware--that would be too crass even for this guy. He's very careful in choosing his words.
1. I haven't read/heard excuses based on updates/features/metrics/&c. as you mention, but their one performance excuse sounds reasonably plausible. Moxie has commented that he'd welcome a PR[0] even if it had bad performance (provided it only ran conditionally of course).
2. The tone in your Github link is a bit heavy-handed, and calling it malware is going too far, but I can understand the developer of software for which security is extremely critical advising strongly against using an outdated version that's being built and distributed by someone else. There is definitely no implication in that comment that F-Droid is malware, he's only referring to TextSecure.
3. I understand your Github link was just to provide an indication of Moxie's tone, but it is very old and the actual factual details in there are probably not very relevant today.
4. I trust the F-Droid software itself, but not necessarily the repository. The distribution of the outdated TextSecure above is as good an example as any - the idea of a 3rd-party building TextSecure and providing it through F-Droid may be all well and good in the spirit of Free Software, but it doesn't really instill trust when the actual author of the software isn't involved at all.
Finally, I'd never heard of the Gandi issues with Moxie's cert before reading that article. After reading it, I'm much more inclined to be suspicious of Gandi than of Moxie. The article is littered with red flags - that fact that their initial response seems to be to go after their customer rather than to question their business relationship with Comodo being a big one.
Do you have reverse engineering experience on Android?
APK uses the zip format. Extract its contents and compare those, minus the META-INF directory, which contains digests and a detached PKCS#7 signature.
Apps whose code output isn't reproducible can still be compared with a varying amount of IDA analysis.
But even if I wanted to build my own apk, and run it on my custom Android build, it would'nt work right? Because of the need for Google Play store?
Verifiable builds are atleast a step in the right direction.
Me neither. How can a bit of software like this obtain any kind of reputation whereas we barely trust openssl anymore is fucking beyond my understanding.........
Can you honestly say that you trust signal over locally or even airgapped pgp'd text?
Realistically, the code in that repo probably isn't even everything that would run on your device even provided you built it yourself.
Bets on some 'fetch js from somewhere' code in there which could completely unfuck the whole thing which acts as a help screen or something that would be very hard to find...
There is literally no way this sort of thing can ever be trusted. Christ, we barely trust PGP anymore...
And be honest, did you really bother to do all that?
Its much harder to make a targeted attack, specially if you are not google or have the full support of google.
Nothing is perfect, but there is very little that is better.
Your other options are only not using the devices at all.
https://github.com/LibreSignal/LibreSignal/issues/37#issueco...
If he said "Please don't use our servers with your custom client, shit might break. You could run your own infra and keep it up to date with us and we'll federate", this would be reasonable.
Instead, if you read that thread a bit more he throws up his hands and says federation is a thing of the past because he had a bad experience with CM. Yeah, because we don't still use federated standards like email and telephony every day. Come on.
https://github.com/LibreSignal/LibreSignal/issues/37#issueco...
This feels a bit like "bad intention". Alternatively you can choose less liberal license, and then make your derivative product from that (Chromium -> Chrome)
Everyone in the geek press said it's "end to end" encrypted! That must mean it's totally safe! I'm sure everyone is reading the source code and building their own clients all the time, yea? Didn't some uber hacker somewhere with a big beard say that he read all the code and it's totally fucking solid and government proof?
Surely you don't mistrust all that do you... I mean... Your seem a bit dubious. You can't be trying to say that there are people out there who are actually not buying this horseshit, that are genuinely withholding trust in these sort of 'services'?
Blasphemy! You think that there are people out there, with a basic grasp of security and cynicism, might feel offended and depressed at how easy it's been to dupe everyone like this.. Again?
Nah. I'm sure we're all totally sold on signal. Seems legit.
I mean, since all the users of such a service have pretty much zero control/visability over the code that's actually running even on their own devices which is talking to this 'service', let alone what's going on on the servers (in some N.American datacentre, probably super secure...) might raise a few eyebrows, but it doesn't really change the fact that we're talking abiut END TO END encryption that someone said was totally 'secure'. And even the media have pushed a few stories about how evil criminals are using it to evade monitoring..
No, I'm not sure I'm on your side. This is clearly totally secure and no one could possibly abuse this kind of thing..
Right?.... Right?
starts crying and loads the rifle
OTR not trusting fingerprint is the default case for any authenticated standard. gnupg requires that you set the trust on a key. Signal allows it initially, warns if it changes.
For all the above though, they aren't a packaged solution that is user friendly. Conversations is a great android client, but there's sadly nothing comparable on iOS (chatsecure, but it's alpha status still). The desktop situation is hit and miss too (I was a pidgin user and moved to bitlbee for OTR, still don't have an omemo solution... though my setup doesn't need it through a TLS secured ZNC).