
Working on AI supported experiences for builder, developers, and all other creators for AWS. Also #BadezimmerVordenker with my own opinions and all that
- Tweets8.2K
- Following620
- Followers813
- Likes136
![I want to accept arbitrary user input. pretends to be grumpy Terry with a sigh Ugh, another one of these requests. YOU WANT TO ACCEPT ARBITRARY USER INPUT?! Do you have any idea how dangerous that is?! First of all, users will obviously try to insert malicious scripts and code to steal data or take down the whole site. Their input could cause Cross Site Scripting (XSS) vulnerabilities left and right. Second, by allowing any ol' input you'll have no control over the type or structure of the data. What if they enter executable files or sensitive information? Now you've got bigger legal and compliance issues to deal with. And don't even get me started on SQL injection! Your database will be wiped clean within minutes if you put untrusted data directly in queries. They'll paralyze the entire application without breaking a sweat. The structural integrity of your code will be demolished. Your entire application will descend into chaos! Do you have any idea how long it'll take me to[...]](https://pbs.twimg.com/media/F_F-mlQW4AAujNo.jpg?name=small&format=webp)
ALT I want to accept arbitrary user input. pretends to be grumpy Terry with a sigh Ugh, another one of these requests. YOU WANT TO ACCEPT ARBITRARY USER INPUT?! Do you have any idea how dangerous that is?! First of all, users will obviously try to insert malicious scripts and code to steal data or take down the whole site. Their input could cause Cross Site Scripting (XSS) vulnerabilities left and right. Second, by allowing any ol' input you'll have no control over the type or structure of the data. What if they enter executable files or sensitive information? Now you've got bigger legal and compliance issues to deal with. And don't even get me started on SQL injection! Your database will be wiped clean within minutes if you put untrusted data directly in queries. They'll paralyze the entire application without breaking a sweat. The structural integrity of your code will be demolished. Your entire application will descend into chaos! Do you have any idea how long it'll take me to[...]

ALT pretends to be grumpy app sec engineer Terry clearing throat loudly Ahem, did you say you want to WRITE YOUR OWN CRYPTO LIBRARY?! Do you have any idea how complex cryptography is?! One tiny mistake and your whole system is hackable! I've been doing this app sec stuff for 30 years and even I wouldn't dream of rolling my own crypto! Let me tell you some of the issues I see here off the top of my bald head: Key management: come on, do you really think you can manage crypto keys better than the pros? One slipped-up sysadmin away from DISASTER. Algorithm choices: AES vs ChaCha vs whatever new fangled thing just came out of a PhD thesis last week. You think you can keep up with the latest research?! Implementation bugs: even the big guys screw it up sometimes. You really think your code is going to be flawless? You'll be giving hackers a nice easy target! Side channels: timing attacks, power analysis, all kinds of juicy side channels just waiting for an expert to exploit.





























