So, the problem with USB tokens that we basically have two choices: - Unauditable black boxes built on *supposedly* more secure ICs that require NDAs to develop for - Open and auditable, but definitely pwnable off the shelf microcontrollers. Which poison do you prefer?
-
-
I was not talking about processor security breaches, or other lab attacks. I master assembly language, more than 1.3 million lines coded and debugged so far, and I can ensure you I know how to code securely like no other high level language can do.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
For example, in assembly language, there are technics from assembly language jedi knights like me to mitigate stack & buffer overflow, but also ROP and maybe JOP (I'd have to review JOP's white paper to ensure my tricks can work). It's all a matter of being an advanced highly
-
Or you could just code in Rust and never have to worry about buffer overflows. Sorry, I would never hire you. You don't know what you're talking about if that's your mindset. If you think coding in assembler means you write more secure code, I am certain your code is not secure.
- Show replies
New conversation -
-
-
trained coder or not. These tricks are coding constraints, that very few people master, but they exist.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.