[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

No DNS poisoning at Google (in case of trouble, blame the DNS)

Subject: No DNS poisoning at Google (in case of trouble, blame the DNS)
From: oscar.vives at gmail.com (Tei)
Date: Thu, 28 Jun 2012 15:46:43 +0200
In-reply-to: <[email protected]>
References: <ED78B1C68B84A14FA706D13A230D7B431954DB1B@ITS-MAIL01.campus.ad.csulb.edu> <[email protected]> <CACg3zYFmwUt78ZhVkWtxuHD0mN1v-Q3_TvDB0Ome2HBAtM9jMQ@mail.gmail.com> <[email protected]>

On 28 June 2012 14:48, Arturo Servin <arturo.servin at gmail.com> wrote:
...
>
> ? ? ? ?Think about sql injection, they are not only to 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.

-- 
--
?in del ?ensaje.

References:
- DNS poisoning at Google?
  - From: Matthew.Black at csulb.edu (Matthew Black)
- No DNS poisoning at Google (in case of trouble, blame the DNS)
  - From: bortzmeyer at nic.fr (Stephane Bortzmeyer)
- No DNS poisoning at Google (in case of trouble, blame the DNS)
  - From: oscar.vives at gmail.com (Tei)
- No DNS poisoning at Google (in case of trouble, blame the DNS)
  - From: arturo.servin at gmail.com (Arturo Servin)

Prev by Date: No DNS poisoning at Google (in case of trouble, blame the DNS)
Next by Date: No DNS poisoning at Google (in case of trouble, blame the DNS)
Previous by thread: No DNS poisoning at Google (in case of trouble, blame the DNS)
Next by thread: No DNS poisoning at Google (in case of trouble, blame the DNS)
Index(es):
- Date
- Thread