comments (not for humans)
"As you saw from your implementation, writing your own security routines isn't always a good idea", Mr. X said looking me straight in the eyes.
[...]
I thought about what Mr. X said for a while.
[...]
"So let's go back to the input validation", Mr. X said. "How do you want to do the validation of the names now?"
[...]
"Now remember", Mr. X said, "that we are storing most of our user data in LDAP. But when we are storing orders, we store the name in our SQL database as a part of the shipping address. How do you suggest we handle LDAP injection with your approach?"
[...]
After finishing the call, Mr. X came back into my office.
[...]
The next morning I got my first go at a real system for a real customer. One of the company's clients had recently had a successful hacking attempt on one of their systems, and they wanted us to review and fix it.
[...]
Today was a disaster - I really messed it up.
[...]
I just posted a new blog entry over at honeynor.no with at analysis of some of the SQL-injection attacks we've seen in Norway lately. Read the full post here: http://www.honeynor.no/2008/11/11/looking-at-some-sql-injection-attacks/[...]
The last couple of days I've been attending NDC2008(Norwegian Developer Conference) here in Oslo. Mats Torgersen's talk on LINQ under the covers was quite interesting.
[...]
I just read Ronald van den Heetkamp's post about hackers using SQL-injection spread malware. The hackers are basically using SQL-injection to inject code that, when opened in a browser, will exploit a security hole in the latest version of flash.[...]