high_byte
Joined 6 years ago
Joined 6 years ago
reminds me of a bug I found in some tplink router it compared passwords of 3 different users but that table was empty so basically 15 NULL bytes would log you in as admin lol
create a skill that transformed the json then "/<skill> <prompt>"
in the olden days (pre-LLMs) we would write high-level code.
the entire layer was high-level code and rarely would we ever need to peak into the assembly:
writing, debugging, architecting, reviewing, testing - all were done in the high-level language layer.
---
welcome to present day:
since we don't write code - we write intents, we also shouldn't review code either - we should review intents.
I don't review my code anymore. I ask the agent to generate markdown docs, graphviz diagrams, changelogs, audit reports, etc. I only review that.
I also ask it to write test and evaluate by whether the tests passed or not. I don't need to peak into the tests code - I can also ask plain english, pseudocode, control flow graph, whatever it is I want.
I can ask it to find errors or missing tests and improve that too!
code is like assembly now.
rare are the cases you would need to peak into that level.
how did this even get approved by app store? that's actually surprising
shame it's not a real device so the surface is limited to bash only
I wonder what software might be vulnerable to this attack surface
I made an app widget to measure time in percentages instead of 24 hours
https://www.reddit.com/r/Time/comments/1ujj9py/comment/ov6qo...