GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Embed Notice

HTML Code

Corresponding Notice

  1. Embed this notice
    Soatok Dreamseeker (soatok@furry.engineer)'s status on Tuesday, 22-Apr-2025 21:27:14 JSTSoatok DreamseekerSoatok Dreamseeker
    in reply to

    Since it's all React.JS, I did the lazy thing: Looked in the assets directory for JavaScript files.

    Success: assets/threads/Threads/encrypt.bundle and assets/threads/Threads/decrypt.bundle.

    Unfortunately, this is just crypto-browserify and some other React libraries webpacked together.

    It's full of side-channels and it's not clear which components are relevant.

    Like, their ghash implementation (used by AES-GCM, which their decrypter uses) uses the && operation after comparing each bit of the state against 0, which short-circuits the right hand side. This introduces a timing side-channel that loudly exposes the entire GHASH state at any given point of time.

    They also implemented AES with S-boxes in pure JavaScript (no bitslicing), which adds a cache-timing leak. Yay.

    Their PKCS7 padding removal step for AES-CBC (which appears to be used for key-wrapping) also maximizes the timing leakage.

    Suffice to say, the only cryptographic primitives I can find in their app are not recommended.

    In conversationabout 2 months ago from furry.engineerpermalink

    Attachments

    1. No result found on File_thumbnail lookup.
      http://together.It/
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.