pending anonymous user

  • 5 Posts
  • 75 Comments
Joined 1 year ago
cake
Cake day: August 7th, 2023

help-circle




  • That scanner is simply looking for high entropy data, and then report to its operator. It wouldn’t care if it is a drive or a volume or a file. If the entropy is high, flag it.

    All random data have high entropy, same for encrypted data. The officer can see you have high entropy data then start throwing questions at you.

    This community need better understanding of cryptography and how it translates to real world. Deniable encryption exists and does work on paper, but only on paper.





  • The point is they don’t have to proof if a piece of random data is indeed an encrypted blob.

    Imagine you passing border security and got selected for search. They found a piece of data on your device with high entropy without known headers in the wrong place. You can claim you know nothing about it, yet they can speculate the heck out of you. In more civil nations, you might got on to a watch list. In a more authoritive nations, they can just detain you.

    They don’t have to prove you hiding something. The mere fact of you have that piece of high entroy data is a clue to them, and they have the power to make your life hard. Oh you said you deny them for a search? First congrats you still have a choice, and secondly that’s also a clue to them.

    For more info, read cryptsetup FAQ section 5.2 paragraph 3, 5.18, and 5.21. It is written by Milan Brož who is way more experienced than me on this matter.




  • XMPP isn’t any better in terms of metadata. OMEMO is an afterthought that slaps on to XMPP. Many metadata are still attached to the message. The threat model only protects the content and doesn’t guard aginst metadata and traffic analysis. Even OMEMO extension is still in experimental status. Not to mention, users still need to signup an account using their email.

    Honestly, I think SimpleX is better in everyway. No account required, minimal metadata (at least from the technical whitepaper and other sources I read), fully open source (AGPLv3), an ok mobile and desktop client, and audited. The register friction is almost non existance. You just need to install, set a name, and off you go. The only worry I have with them is they took VC funds.

    ADD: XMPP is still better for company internal communication, especially when compliances require conversation archiving.





  • OP, I understand what you look for, but that’s not easy task. From my limited knowledge of apps development, achieving what you requested would likely be:

    1. Identify and remove all relevent code to the backend. Easier if it’s modular, very hard if they’re litrered everywhere.
    2. Chose a XMPP client library that have relavent extension support that can translate Telegram features that XMPP understands.
    3. Write an adaptor (if modular) to match the methods signature and translates calls to the client library. Or reimplement all the code you removed (if littered everywhere) with the client library.

    This is akin to swaping to a new engine for a car, with incompatible mounts. Diffcult to execute, and (I believe) low interest. You can try if you got the skills. I don’t and even I have, I will just use SimpleX which fits my needs.