• tribut@infosec.pub
    link
    fedilink
    arrow-up
    4
    ·
    12 days ago

    Cleatext signing (having the signature and data in the same file) is broken in many ways. It is possible to put unsigned data at the top of the file in a way that sha256sum will use it. Watch the 39c3 GPG talk if your interested in the gory details.

    The solution is to use detached signatures (checksum.txt and checksum.txt.gpg to verify that). This makes sure that all of checksum.txt is actually covered by the signature.

    • Walters, Fern@bookwyr.me
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      12 days ago

      cc @[email protected]
      or, binary signatures, [which I prefer: compressionable], as textfiles are insecure formats.

      I prefer a headed, mided, and tailed verification, similar to MPEG keyframing, for constant stream verification.

      • lurch (he/him)@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        12 days ago

        idk about the specific formats, but i don’t think you can say that in general. what are those two formats and why does it make a difference in this case?

        • Walters, Fern@bookwyr.me
          link
          fedilink
          English
          arrow-up
          1
          ·
          12 days ago
          1. what binary signatures offer:
          • smaller sizes
          • ability to compression
          • the actually signature
          • confidentiality
          1. File headersdef, midingdef, tailingdef.

          2. why textfiles are insecure

          i don’t think you can say that in general

          What is your academic literacy please?

          Cite your papers please.

          or gen z:
          Drop your academic flex.
          What grade you at?
          papers pls🙏

          orly

          • lurch (he/him)@sh.itjust.works
            link
            fedilink
            arrow-up
            1
            ·
            11 days ago

            no, i mean, you say text files are insecure and you prefer binary.

            while it is true that processing text files needs additional code (validating/converting charsets/encoding), which increases the number of potential attack vectors, security threats introduced by this are not a fault of them being text, but of the parser code.

            at the end of the day the attacker just switches from text editor to hex editor to prepare a malicious file.

            • Walters, Fern@bookwyr.me
              link
              fedilink
              English
              arrow-up
              1
              ·
              10 days ago

              I was never talking about vectorization, but regular file integrity. Textfiles have no error correctiveness. Yet a binary can be. Either can be edited and vectorized. Heck the point of this talk is manipulating expectations, as sha256sum isn’t file verifier.

              • lurch (he/him)@sh.itjust.works
                link
                fedilink
                arrow-up
                1
                ·
                10 days ago

                yeah, but nobody stops you from adding error correctiveness. you could for example just put the whole thing three times with a seperator.

                however there’s also an important point for text files: you can post them wherever you can write text messages. being able to digitally sign them even adds to your freedom, as you can post anonymously and your readers are able to verify it’s from the same source. like you could post your heated political manifesto or cousin incest smut on 4chan or some darknet forum and if you later make a part 2, ppl will be able to tell you apart from imposters.