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?
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.
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.
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.
cc @modem_down@thebrainbin.org
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.
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?
File headersdef, midingdef, tailingdef.
why textfiles are insecure
What is your academic literacy please?
Cite your papers please.
or gen z:
Drop your academic flex.
What grade you at?
papers pls🙏
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.
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
sha256sumisn’t file verifier.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.