4 ms·
The thing about Classic ASP is that it has no in-built protections and the individual developer has to code all defence, which is not great. Also, how many cla
by raesene9 5y ago
The thing about Classic ASP is that it has no in-built protections and the individual developer has to code all defence, which is not great.
Also, how many classic ASP developers are there now , to add new protections for new issues...
And if you look at the linked thread, it doesn't seem like they've done a great job of maintenance...
- giardini 5y agoraesene9 says >"The thing about Classic ASP is that it has no in-built protections and the individual developer has to code all defence,,,"< Yes, it is just like PHP or Perl or Ruby with the CGI specification. raesene9 says >" how many classic ASP developers are there now ..."< Good question! But IMO a web developer could learn classic ASP in a single day!8-)) raesene9 says >"the individual developer has to code all defence,< Yes, just like PHP or Perl or Python.
- raesene9 5y agoSure so they learn classic ASP in a day, now they have to code their own custom routines for XSS protection, SQLi Protection, SSRF protection etc etc etc or.... they could move the application to a supported platform with a wider developer base and in-built protections against common web application security attacks. There is a reason why most web app developers do not hand code their entire stacks. For example why ruby web developers use rails. Web app. sec. is a a relatively complex field to get right, full of edge cases. Having each and every web app development team take the time to understand all those cases and edges probably isn't the best use of scarce developer resources.