your editor go crazy and show you things that aren't in the file?
If your editor won't show the code only because you use gibberish, change the code editor immediately
Tell me the name of editor that has never had, doesn't have and will never have bugs.
Not having bugs hiding parts of the malicious code? Any of them
One exploit can be used to create another. Software is complicated and can be manipulated in lots of ways. Not all of which are known.
This is mere speculation or trolling To create a malicious code using an inexistent vulnerability in your code editor
You can't prove that something is inexistent. I'm not trolling, I'm being 100% serious.
My statement is "there might be an editor that might have a vulnerability that might be used to cause it to display text in a wrong way". There is no way for you to prove me wrong on this.
You have to read the scientist method first
You're simply spreading fud with zero arguments about an inexistent bug still unknown
At no point have a I claimed that something like that exists. The only thing I claim is that it might.
Ok, so this issue is inexistent
You can't claim nonexistence of anything.
I have to disagree here. It is true that most editors' vulnerabilities have to do with malformed input, where they can be crashed (i.e. denial of service), or in some cases achieve code execution. It is also true that technically, you could insert non-printable control characters in a text file, especially if you have a hex editor and an ASCII conversion chart handy. And I do encourage security research like this, especially fuzzing. If anything, developers should not consider any data provided by the user or third-party code trustworthy at all. However, and this is where I disagree.. if you break the text viewer / editor like this, chances are that you'll also break the AUR helper's code that interprets such a malformed file. There is still a syntax to it, and that has to be taken into account. Inserting non-printable control characters would not only be a giant red flag, it would also most likely not work.
It's not something that can always be picked up easily.
Unicode attacks on source code have gained traction in recent years. For reference: https://en.m.wikipedia.org/wiki/Trojan_Source http://unicode.org/reports/tr55/ https://unicode.org/reports/tr39/
Tell this to @il_muflone ._.
Обсуждают сегодня