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

2012-07-03 Thread Kyle Creyts
it actually appears that skywire has a suballocation for that block, http://www.robtex.com/ip/208.88.11.111.html#whois # # The following results may also be obtained via: # http://whois.arin.net http://www.robtex.com/dns/whois.arin.net.html /rest/nets;q=208.88.11.111

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

2012-07-03 Thread Kyle Creyts
and upon further investigation, it seems like there might be an actual organization using a host with that IP... http://www.robtex.com/dns/chatwithus.net.html#shared On Tue, Jul 3, 2012 at 2:27 PM, Kyle Creyts kyle.cre...@gmail.com wrote: it actually appears that skywire has a suballocation

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

2012-06-28 Thread Tei
On 27 June 2012 09:50, Stephane Bortzmeyer bortzme...@nic.fr wrote: (trollspecially for a Web site written in PHP/troll)? We software makers have a problem, when a customer ask for a application, often theres a wen project that already do it ( for the most part is a round peg on a round hole).

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

2012-06-28 Thread Arturo Servin
On 28 Jun 2012, at 08:05, Tei wrote: On 27 June 2012 09:50, Stephane Bortzmeyer bortzme...@nic.fr wrote: (trollspecially for a Web site written in PHP/troll)? We software makers have a problem, when a customer ask for a application, often theres a wen project that already do it ( for

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

2012-06-28 Thread Tei
On 28 June 2012 14:48, Arturo Servin arturo.ser...@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

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

2012-06-28 Thread Ken A
On 6/28/2012 6:05 AM, Tei wrote: If you use these project that already do 99% of what the customer need, plus a 120% the customer not need (and perhaps don't want). The code quality will be normally be good, with **horrible** exceptions. But sooner or later, (weeks) there will be exploits for

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

2012-06-27 Thread Daniel Rohan
On Wed, Jun 27, 2012 at 10:50 AM, Stephane Bortzmeyer bortzme...@nic.frwrote: What made you think it can be a DNS cache poisoning (a very rare event, despite what the media say) when there are many much more realistic possibilities (trollspecially for a Web site written in PHP/troll)? What

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

2012-06-27 Thread Arturo Servin
It was not DNS issue, but it was a clear case on how community-support helped. Some of us may even learn some new tricks. :) Regards, as Sent from mobile device. Excuse brevity and typos. On 27 Jun 2012, at 05:07, Daniel Rohan dro...@gmail.com wrote: On Wed, Jun 27, 2012 at 10:50 AM,

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

2012-06-27 Thread Jason Hellenthal
What would be nice is the to see the contents of the htaccess file (obviously with sensitive information excluded) On Wed, Jun 27, 2012 at 10:14:12AM -0300, Arturo Servin wrote: It was not DNS issue, but it was a clear case on how community-support helped. Some of us may even learn some

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

2012-06-27 Thread Ryan Rawdon
On Jun 27, 2012, at 9:26 AM, Jason Hellenthal wrote: What would be nice is the to see the contents of the htaccess file (obviously with sensitive information excluded) I cleaned up compromises similar to this in a customer site fairly recently. In our case it was the same exact behavior

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

2012-06-27 Thread Ryan Rawdon
On Jun 27, 2012, at 10:10 AM, Ryan Rawdon wrote: On Jun 27, 2012, at 9:26 AM, Jason Hellenthal wrote: What would be nice is the to see the contents of the htaccess file (obviously with sensitive information excluded) I cleaned up compromises similar to this in a customer site

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

2012-06-27 Thread Matthew Black
Ask and ye shall receive: # more .htaccess (backup copy) #c3284d# IfModule mod_rewrite.c RewriteEngine On RewriteCond %{HTTP_REFERER} ^.*(abacho|abizdirectory|acoon|alexana|allesklar|allpages|allthesites|alltheuk|alltheweb|alt

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

2012-06-27 Thread Matthew Black
By the way, FTP access originated from: 208.88.11.111 Sky Wire Communications SKYWIRE-SG (NET-208-88-8-0-1) 208.88.8.0 - 208.88.11.255 NetRange: 208.88.8.0 - 208.88.11.255 CIDR: 208.88.8.0/22 OriginAS: AS40603 NetName:SKYWIRE-SG NetHandle: NET-208-88-8-0-1

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

2012-06-27 Thread AP NANOG
On 6/27/12 12:51 PM, Matthew Black wrote: Ask and ye shall receive: # more .htaccess (backup copy) #c3284d# IfModule mod_rewrite.c RewriteEngine On RewriteCond %{HTTP_REFERER} ^.*(abacho|abizdirectory|acoon|alexana|allesklar|allpages|allthesites|alltheuk|alltheweb|alt