@peregus It's explained in other threads here. The key is in the url but behind # and that part is invisible to the server. protocol://host:port/path?query#fragment, server will only see ..?query, so both participants can decrypt, but server can't => E2EE

[–] peregus@lemmy.world 1 points 2 weeks ago (1 children)

But it's the server that creates the URL in the first place, so it must knows it, right? ...or wrong?

[–] chebra@mstdn.io 1 points 2 weeks ago (1 children)

@peregus No that would be created by javascript in the sender's browser.

[–] peregus@lemmy.world 1 points 2 weeks ago (1 children)

Oh, ok, now I get it. So it could be checked by a third party if that code is really created by the browser and if it's not sent to the server, correct?

[–] chebra@mstdn.io 0 points 2 weeks ago (1 children)

@peregus yes, that would be here: https://github.com/timvisee/send/blob/master/app/fileSender.js#L81

[–] peregus@lemmy.world 1 points 2 weeks ago (1 children)

@chebra@mstdn.io but the owner of the server could change it, could it be checked directly on the webpage of the service? Not that I will do it (I can't, I can't read that code), I'm just curious.

[–] chebra@mstdn.io 2 points 2 weeks ago (1 children)

@peregus yes, well the javascript on the site is minified, but I found this place even in the minified code. At this level it would be easier to take the source code and compile your own, host your own instance, then you know exactly what code is running there. And their minified code could be directly compared with your minified code... the beauty of open-source software.

[–] peregus@lemmy.world 2 points 2 weeks ago (1 children)

@chebra@mstdn.io Thanks a lot for your time explaining that to me!

[–] chebra@mstdn.io 1 points 2 weeks ago

@peregus You're welcome, stay curious!