[154207] in North American Network Operators' Group
Re: No DNS poisoning at Google (in case of trouble, blame the DNS)
daemon@ATHENA.MIT.EDU (Tei)
Thu Jun 28 09:48:36 2012
In-Reply-To: <EC510E89-420B-4367-BB1D-44D0CACB487C@gmail.com>
From: Tei <oscar.vives@gmail.com>
Date: Thu, 28 Jun 2012 15:46:43 +0200
To: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 28 June 2012 14:48, Arturo Servin <arturo.servin@gmail.com> wrote:
...
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0Think about sql injection, they are not only t=
o specific platforms but to general bad programming practices.
If you are already a good programmer, writing code that is safe
against sql inyections is trivial. So is not a real problem, and
thats why I don't mention it. A real problem is one that you can't
avoid by just walking one step to the left.
But I support that you champion it, and I fully agree bad code is
possible and some people do write it. We don't really disagree.
--=20
--
=E2=84=B1in del =E2=84=B3ensaje.
