shared-phrase collision #1

New issue

Closed

opened 2022-08-16 04:56:52 +02:00 by fgardt · 2 comments

fgardt commented

2022-08-16 04:56:52 +02:00

(Migrated from github.com)

Since the shared-phrase is user chosen it is possible that more than 1 send and receive party use the same phrase at the same time on the same helper server.

Right now this could cause either

mixup of receiver B receiving data from sender A and vice versa
both senders to "connect" to each other and sending data at each other while the receivers get no data at all

The solution would be to let the helper server generate a phrase that is not in use at the moment and send it back to the sender. The sender then can forward the phrase to the receiver and everything else then works like usual.

This reminds me a lot of croc.

Since the `shared-phrase` is user chosen it is possible that more than 1 send and receive party use the same phrase at the same time on the same helper server. Right now this could cause either 1. mixup of receiver B receiving data from sender A and vice versa 2. both senders to "connect" to each other and sending data at each other while the receivers get no data at all The solution would be to let the helper server generate a phrase that is not in use at the moment and send it back to the sender. The sender then can forward the phrase to the receiver and everything else then works like usual. _This reminds me a lot of [croc](https://github.com/schollz/croc)._

TudbuT commented

2022-08-16 08:01:36 +02:00

(Migrated from github.com)

I'll see what I can do. I would really like to keep it in such a way that order of connection of sender and receiver is irrelevant, but I don't think that is possible. This won't be top priority until some more sending and receiving issues are fixed, but once those are done, I'll fix this one.

About croc: QFT is peer-to-peer, croc uses a relay.

TudbuT commented

2022-10-02 23:30:43 +02:00

(Migrated from github.com)

Won't fix, i dont want to use random phrases as those generally suck, maybe i will find a nice solution soon, but for now, i don't think i have a solution here.