<br><br><div class="gmail_quote">On Mon, Apr 15, 2013 at 3:02 AM, Adam Nelson <span dir="ltr"><<a href="mailto:adam@varud.com" target="_blank">adam@varud.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I brought it up a few months ago in Skunkworks, but until the .ke top level domain is signed, </div></blockquote><div><br></div><div><br></div><div>of course, you have to sign .<a href="http://co.ke">co.ke</a> AND <a href="http://google.co.ke">google.co.ke</a> for DNSSEC to mitigate against cache poisoning.</div>
<div><br></div><div>�</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">you can't really trust the identify of any site under .ke that doesn't use an SSL certificate (i.e. the regular <a href="http://google.co.ke" target="_blank">google.co.ke</a> without "https").<div>
<br></div><div><div style="font-family:arial,sans-serif;font-size:13px"><a href="http://stats.research.icann.org/dns/tld_report/" target="_blank">http://stats.research.icann.org/dns/tld_report/</a></div><div><br></div><div>
I'm pretty confident that Google's systems weren't cracked and that this was something like a DNS attack on one of the ISPs or similar.</div><div><br></div></div></div></blockquote><div><br></div><div>Probably:</div>
<div><br></div><div><p style="color:rgb(0,0,144);font-size:13px;font-family:Arial,Helvetica,sans-serif;background-color:rgb(240,240,255)">�here is the�<b>dig</b>�result for�<b><a href="http://google.co.ke">google.co.ke</a></b>�from server 8.8.8.8 [dig @<a href="http://8.8.8.8">8.8.8.8</a> <a href="http://google.co.ke">google.co.ke</a> A]</p>
<table border="1" cellpadding="10" cellspacing="0" style="color:rgb(0,0,144);font-size:12px;font-family:Arial,Helvetica,sans-serif;background-color:rgb(240,240,255)"><tbody><tr style="font-size:12px"><td class="G2" style="font-size:12px;font-family:Arial,Helvetica,sans-serif">
<pre style="font-size:13px;font-family:Courier,Mono,monospace">
; <<>> DiG 9.7.3 <<>> @<a href="http://8.8.8.8">8.8.8.8</a> <a href="http://google.co.ke">google.co.ke</a> A
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38419
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;<a href="http://google.co.ke">google.co.ke</a>. IN A
;; ANSWER SECTION:
<a href="http://google.co.ke">google.co.ke</a>. 300 IN A 173.194.35.152
<a href="http://google.co.ke">google.co.ke</a>. 300 IN A 173.194.35.151
<a href="http://google.co.ke">google.co.ke</a>. 300 IN A 173.194.35.159
;; Query time: 17 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Apr 15 14:16:38 2013
;; MSG SIZE rcvd: 78
</pre></td></tr></tbody></table></div><div><br></div><div><br></div><div><a href="http://whois.arin.net/rest/net/NET-173-194-0-0-1/pft">http://whois.arin.net/rest/net/NET-173-194-0-0-1/pft</a></div><div><br></div><div><br>
</div></div>-- <br>Cheers,<br><br>McTim<br>"A name indicates what we seek. An address indicates where it is. A route indicates how we get there."� Jon Postel