like, if I send the QR code to someone I want to talk to via email, anyone intercepting this message will at the very least know my SimpleX address; same thing if I send it via messenger.

edit: let’s assume we don’t have an established and trusted channel. furthermore, they’re not expecting this info.

  • Eggroley@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    Send the address and delete it after you’ve verified that the recipient is in your simplex contacts. You can verify via security code. You’ll know when they use the link. Delete the address afterwards.

  • HandwovenConsensus@lemm.ee
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Well, there’s not much they can do with the QR code. You can deactivate it as soon as you’ve made contact and established proof of identity with the recipient.

    But, if it was really important, there are cryptographic key-exchange protocols you can do even over an insecure connection. The Diffie-Hellman key exchange is one of them. Using something like that, you can derive a shared secret key even if someone’s listening.

    But personally, I would just break it into two parts, and send one by email and one with pastebin’s “burn-after-read” option.

  • Evgeny Poberezkin@lemmy.mlM
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    You don’t have to encrypt the message, simply observing it won’t compromise security. You only need to ensure that the channel is 1) authenticated (that is, you know who you send to) 2) cannot MITM you (that is, replace the link). MITM can be mitigated with security code verification via yet another channel, but SimpleX relays cannot MITM key exchange (unlike any centralised service).

  • jet@hackertalks.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 months ago

    Without face-to-face communication, you cannot guarantee you haven’t been man in the middle MITM.

    One of the benefits of public key cryptography, is everybody can publish their public key, and then you can have a reasonable assurance that you’re talking to the appropriate person, cuz you can see the key, they can see the key, so in theory you have verified the key.

    With simple x, if one of you publishes a known non-incognito, static receive address. IE on your public website, or in your letterhead, or something, then the other side knows they’re talking directly to you. You don’t know you’re talking directly to them. Or at least to the published address

    If you want to talk to somebody, in a deniable way, then you probably should not be sending them direct mail. Meet them in person, exchange addresses that way, use briar, something.