News for hackers. Stuff that matters.
Re:End to End Encrypted, Private Search by rasengan on Wednesday March 03, 2021 @11:58AM (#26331130)
Thanks for taking a look, and that's a great question. The search is both end to end encrypted and private.

In the sense of end to end, if you rely on TLS alone and send your query directly to the search engine, your IP will be attached to said query and thus your search and identity are coupled.

In private.sh, it's both end to end and private:

1. We utilize client-side javascript encryption prior to routing a search thru a proxy.

2. The proxy cannot read the query, and simply forwards it to the search engine.

3. The search engine decrypts, performs the search, and encrypts the results which are sent back thru the proxy (who, again, cannot even read the results).

4. The results are decrypted client-side.

Thus, your search query and identity are decoupled.

Re:End to End Encrypted, Private Search by lucb1e on Wednesday March 03, 2021 @12:28PM (#26331612)
That's very similar to what Tor does. And since both parts are under control of the same actor, it's not very different from, well, not doing it.

But too often ideas are shot down because they're not "helpful enough" or something. I shouldn't be too critical! It's great to see someone working privacy in the search space beyond tech that is already there. Having tor-like anonymity without needing to use a special browser and slow network is definitely an advantage, perhaps we can iterate upon the design later (somehow introduce user-run proxies so that the search server really cannot know who sent the request? Somehow make the javascript reload only every once in a while, so you can't silently change it for everyone at once as an attacker? People monitoring the subresource integrity tags for unexpected changes? I don't know). I'll be curious to see where this takes us!

Re:End to End Encrypted, Private Search by rasengan on Wednesday March 03, 2021 @01:41PM (#26332601)
> And since both parts are under control of the same actor, it's not very different from, well, not doing it.

Both parts are not in control of the same entity.

That said, thanks for the input and comments!

Edit: If you have any more input on how it can be approved, I would love to hear it! :-) My email is in my profile!

Re:End to End Encrypted, Private Search by lucb1e on Wednesday March 03, 2021 @02:51PM (#26333453)
> Both parts are not in control of the same entity.

How does that work? Do you or a subcontractor of yours not host the javascript responsible for the encryption?

Edit: okay so this piqued my interest and the site has this to say: "Public IP is stripped away by the Private.sh proxy" (so you run the proxy) and "Search Provider decrypts the query". So the point is that Privacysh != Search Provider I guess? That begs the question whether one is a subcontractor or side project of the other, or hosted in the same physical space, or something else that make this effectively the same as not proxying it. Also because you need to coordinate on what JS is being delivered to some extent: if Privacysh doesn't use the right pubkey, the SP can't decrypt it.

It feels a bit like Telegram who says "all our chats are encrypted, really! We can't read your messages!" but is still somehow able to deliver the plaintext messages to your client at a very fast rate. The trick being that "the key is stored in another datacenter as the message" but of course Telegram owns both and that's how they combine it for intercepting, ahem, for delivering messages to your phone. This isn't the same, but without more background info it seems similar. Then again, it can't be worse than the status quo, so still good that you're working on this one way or another!

Re:End to End Encrypted, Private Search by rasengan on Wednesday March 03, 2021 @03:14PM (#26333769)
> Then again, it can't be worse than the status quo, so still good that you're working on this one way or another!

Thank you. To clarify, private.sh != search provider (gigablast). Thus, it would take collusion between both to couple the identity of the searcher to the search query.

private.sh does not have access to the private key associated with the public key that's used to encrypt the search query!

Re:End to End Encrypted, Private Search by lucb1e on Wednesday March 03, 2021 @03:20PM (#26333852)
Thanks for clarifying, that's a setup I definitely haven't seen before. Interesting!
Re:End to End Encrypted, Private Search by bawolff on Wednesday March 03, 2021 @02:59PM (#26333582)
> Both parts are not in control of the same entity.

That seems doubtful. Which party is in control of the end where decryption takes place if not private.sh?

Re:End to End Encrypted, Private Search by rasengan on Wednesday March 03, 2021 @03:03PM (#26333641)
The search (where decryption takes place) is controlled by GigaBlast.com.
Re:End to End Encrypted, Private Search by bawolff on Wednesday March 03, 2021 @03:11PM (#26333749)
Fair enough, i guess that's something.
Re:End to End Encrypted, Private Search by dwohnitmok on Wednesday March 03, 2021 @01:43PM (#26332625)
> Having tor-like anonymity without needing to use a special browser and slow network is definitely an advantage

This is potentially huge. Maybe for a resource-light webpage (in terms of content downloaded by the user) the overhead of a Tor onion architecture is negligible and combined with being able to use your regular old browser with no special configuration, that could mean just having specialized onion architectures for certain websites could make privacy a lot easier to realize for the end user.

The barriers of slow load times for every webpage and the need for end user configuration are pretty big barriers.

Re:End to End Encrypted, Private Search by lucb1e on Wednesday March 03, 2021 @02:54PM (#26333499)
I mean, there's a reason we're not commonly doing this: a setup where the relaying and the back-end component are from the same organisation make it fairly useless. You need to find an established partner that wants to work with you to have some claim to not be colluding. And even if so, the front-end can always deliver another piece of javascript that carries off a copy of the plaintext to a server of their own. This setup has some clear disadvantages over Tor. But to repeat what I said before: I shouldn't be too critical when all I'm really saying is "it might not help enough to be worth the effort". If there are no downsides either (well, the effort, but that's up to the dev and consequently the user who pays the dev indirectly) then it's better to do it.
Re:End to End Encrypted, Private Search by bawolff on Wednesday March 03, 2021 @03:01PM (#26333604)
This is not tor like anonoyminity. At best this is like vpn-level anonoyminity.
Re:End to End Encrypted, Private Search by deanclatworthy on Wednesday March 03, 2021 @12:00PM (#26331172)
If you're going to rely on any client-side javascript please use subresource integrity for all your assets.
Re:End to End Encrypted, Private Search by speedgoose on Wednesday March 03, 2021 @12:18PM (#26331439)
If TLS is compromised, you cannot trust the subresource subresource integrity checksums. It's better than nothing but there is no good solution.
Re:End to End Encrypted, Private Search by rasengan on Wednesday March 03, 2021 @03:49PM (#26334294)
Our solution here is our extensions [1][2] which are hosted and served by google and mozilla (third parties).

[1] https://chrome.google.com/webstore/detail/privatesh-private-...

[2] https://addons.mozilla.org/en-US/firefox/addon/private-sh-pr...

Re:End to End Encrypted, Private Search by bawolff on Wednesday March 03, 2021 @03:05PM (#26333659)
Which is why this whole exercise is a bunch of snake oil. You can't have better than TLS security when TLS is the weakest link.
Re:End to End Encrypted, Private Search by blueplanet200 on Wednesday March 03, 2021 @03:52PM (#26334332)
This is just plain false. This search engine is advertising anonymity. You don't get that when searching Google, which is encrypted with TLS...
Re:End to End Encrypted, Private Search by blueplanet200 on Wednesday March 03, 2021 @12:28PM (#26331620)
Indeed, if TLS is compromised many security guarantees of the web break down.
Re:End to End Encrypted, Private Search by yikesshescute on Wednesday March 03, 2021 @01:17PM (#26332328)
How do I verify that my query is being encrypted in the browser?

And is the proxy a service under your control?

Re:End to End Encrypted, Private Search by rasengan on Wednesday March 03, 2021 @02:42PM (#26333319)
The javascript source should show you that it's being encrypted -- and the proxy is under our control, the search engine is not.
Re:End to End Encrypted, Private Search by yikesshescute on Wednesday March 03, 2021 @04:50PM (#26335160)
Then every time I want to make a query I must re-audit the JavaScript source?

And, do you have any ideas about setting up the proxy so that I don’t have to trust that it is being operated as advertised?

Re:End to End Encrypted, Private Search by judge2020 on Wednesday March 03, 2021 @01:21PM (#26332381)
Given that no external domain is contacted to pull the public key to encrypt with, how do we know the proxy won't send its own public key to the browser then forward the query to the search engine via a different encrypted payload?
Re:End to End Encrypted, Private Search by rasengan on Wednesday March 03, 2021 @03:51PM (#26334315)
In this case, the only way to be sure of this is to use the private.sh extension[1] which has the public key hardcoded in and is being served by google and mozilla.

[1] https://private.sh/extension.html