Live data from Hacker News

Darknet Messenger Briar Releases Beta, Passes Security Audit

briarproject.org

71–80 of 90 posts

Re: Darknet Messenger Briar Releases Beta, Passes Security Audit

#71
post #54

Earlier quoted context omitted.

Elaborate, or refrain from posting messages like that.

It is a term used by media and seen by general public when talking about many unethical or illegal things like child pornography and drug marketplaces, so perhaps not the best thing to associate with in your marketing material.

So should we stop saying "hackers" because it is also a term used by media and seen by the general public when talking about many unethical or illegal things?

Re: Darknet Messenger Briar Releases Beta, Passes Security Audit

#72

"Darknet" is a brainwashing propaganda term. Please do not use it, thanks.

What is the right term then?

Who knows? The whole problem is that "darknet" is a label that doesn't mean anything definite, a buzzword but not a term.

You may say that a tool/network/protocol is decentralized and/or secure and/or anonymous and/or censorship-resistant and/or routed through Tor and/or doesn't leak identity and/or tamper-resistant and/or has plausible deniability etc etc and all these labels would mean something - "darknet" does not.

A "darknet messenger" might tick any set of these boxes, but the meaning is completely different depending on which of these labels apply.

Re: Darknet Messenger Briar Releases Beta, Passes Security Audit

#73
post #67

Earlier quoted context omitted.

How about "secure against spying by governments and criminals".

So 'highly secure' would be better than darknet

Not quite, because that leaves out the important fact that it doesn't operate over typical networks.

Re: Darknet Messenger Briar Releases Beta, Passes Security Audit

#74
post #32

Earlier quoted context omitted.

Maybe I'm missing something, but if the protocol were well defined and open source, it would be trivial to detect, no?

Not really, the idea would be to hide data by using different amounts of spaces in text files, in the least significant bits of pixels in images, or in the access pattern to a certain service. The data looks like legitimate traffic. You could run the tool on absolutely all traffic, but that would be computationally intensive. And the data you get out is still encrypted, so ideally you can't tell if it is random (from…

"the idea would be to hide data by using different amounts of spaces in text files, in the least significant bits of pixels in images, or in the access pattern to a certain service" is not appropriate for the claimed use case, i.e. activists in totalitarian regimes.

In such an environment, the traffic of suspected activists will be analyzed.

Assuming the kernels are open, it's possible to see in analysis of certain data that "amounts of spaces in text files, in the least significant bits of pixels in images, or in the access pattern to a certain service" have encoded information, even if the extracted information looks like random/encrypted data. At this point you don't have plausible deniability and rubber hose cryptoanalysis can be used.

Switching to new kernels happens too late since you don't know when they've identified a kernel until they start arresting people - it's not like they're simply going to block it immediately.

i.e., the described service is resistant to mass censorship and automated filtering, but these use cases actually need to be able to resist attribution and retaliation, which are quite different problems.

Re: Darknet Messenger Briar Releases Beta, Passes Security Audit

#75
When I see that one of the requirements for privacy-preserving software is to have been in the same physical location as the person I need to connect with, while running said software, I immediately stop reading and move on to other things.

I've done this for roughly five years.

Assuming I've never wanted to become a Debian developer, is there any important piece of privacy-preserving software I've missed out on? Is there likely to be any important privacy-preserving software I will miss out on in the next five years?

Edit: clarification

Re: Darknet Messenger Briar Releases Beta, Passes Security Audit

#76
As for the audit[1], how would HTML sanitization on sender side protect the reader? On page 12 they suggest adding "HTML sanitization" in onSendClick function. It is as lame as protecting against XSS with JavaScript. Attacker will simply remove this code and recompile app.

[1] https://briarproject.org/raw/BRP-01-report.pdf

Re: Darknet Messenger Briar Releases Beta, Passes Security Audit

#77

This looks interesting, but I wonder how safe it is in the stated use case of journalists, activists in an authoritarian country. It can use Tor, which hides whom you are communicating with, but the fact that you are using Tor sticks out like a red thumb. The authorities probably just have to flip a switch to put you under closer surveillance if they see you use Tor. Or they'll just send someone to your registered ad…

Briar is designed with a distinct transport layer so it is entirely possible to support this type of thing.

Re: Darknet Messenger Briar Releases Beta, Passes Security Audit

#78

When I see that one of the requirements for privacy-preserving software is to have been in the same physical location as the person I need to connect with, while running said software , I immediately stop reading and move on to other things. I've done this for roughly five years. Assuming I've never wanted to become a Debian developer, is there any important piece of privacy-preserving software I've missed out on? Is…

Short of web of trust, which has other issues, how else would you propose to bootstrap?

Re: Darknet Messenger Briar Releases Beta, Passes Security Audit

#79

As someone who does professional security audits, I would just like to say that there is no such thing as "passing" a security audit. In fact, most pen testing shops will carefully dance around actually making that claim in writing for a customer, because they know they are going to look bad when a bug is inevitably found in code they reviewed (and it's probably a dumb idea for liability reasons too). There are certa…

I haven't looked at the audit yet (and agree with your comments), but I can say a bit about what Briar is doing with crypto.

The focus is on a time window based hash derivation of keys for symmetric cryptography and tags to recognize streams. It currently uses blake2s and XSalsa20/Poly1305. Bouncy Castle is used for the core algorithm implementations when possible.

Connections are made via QR code and use ECDH with cofactor multiplication. There is also a simple bittorrent-inspiried synchronization level that is new and an encrypted storage layer for data storage (I'm not sure but I think this may use pre-existing code).

So there is some amount of crypto to look at but it is fairly basic and not doing anything exotic. The layering and heavy use of symmetric crypto makes the crypto simpler than might be expected based on the features (and battery use heavier).

Version 1 of anything is likely to have issues and hopefully even the release will have a disclaimer to that effect, but there is always a tradeoff between needing some amount of support for further development and trying to make the best app possible before releasing. Briar has been in development for years and they are aware of that tradeoff and trying to both be cautious and not allow the project to die from lack of usable result.

The transport layer spec is at: https://code.briarproject.org/akwizgran/briar-spec/blob/mast...

QR code based key exchange spec is at: https://code.briarproject.org/akwizgran/briar-spec/blob/mast...

Sychronization layer spec is at: https://code.briarproject.org/akwizgran/briar-spec/blob/mast...

Re: Darknet Messenger Briar Releases Beta, Passes Security Audit

#80

As someone who does professional security audits, I would just like to say that there is no such thing as "passing" a security audit. In fact, most pen testing shops will carefully dance around actually making that claim in writing for a customer, because they know they are going to look bad when a bug is inevitably found in code they reviewed (and it's probably a dumb idea for liability reasons too). There are certa…

I was not aware of the tarsnap issue, but for anyone else wondering, I think it's this: http://www.daemonology.net/blog/2011-01-18-tarsnap-critical-...
Post reply on HN