a. Poor dashboard design. The glove compartment and the area on the right side of the steering is protruding out. As a result, your knee hit the same when you get in or get out of the car. Initially I thought that may be seat is not pushed back properly so I pushed it back but still  I faced this every time I tried to get in. Pics below clearly illustrate the same.

The pictures below clearly show that the lower part of the dashboard protrudes out far more in the NEW Honda City compared to the OLD Honda City ZX.

I am surprised that Honda engineers missed out such a design issue.

You may want to try it yourself. Its painful when your knee hits the dashboard.

2. Roof height on the back seat. My head touches the roof when I sit on the back seat. I am 5’11″ which is an average height, not too tall.

So, as it turns out, the car is not comfortable for the driver or the passenger sitting at the back.

I am however hopeful that Honda will correct these issues soon. Infact I shared this feedback with the the Honda sales representative and she said:

Sir, we have the same feedback from other customers as well. We know about these two issues.

I just hope that they pass on the feedback to Honda or else Honda reads my post.

Have you also test driven the car? Did you also face these issues? Do share.

I checked mine and learnt that its not safe. My service provider is Airtel. Here is what I got?

Your name server, at 202.56.215.76, appears vulnerable to DNS Cache Poisoning.

All requests came from the following source port: 53541

Due to events outside our control, details of the vulnerability have been leaked. Please consider using a safe DNS server, such as OpenDNS. Note: Comcast users should not worry.

---

Requests seen for 41ec59db53bf.doxdns5.com:
202.56.215.76:53541 TXID=39666
202.56.215.76:53541 TXID=36131
202.56.215.76:53541 TXID=33110
202.56.215.76:53541 TXID=8581
202.56.215.76:53541 TXID=58442

What is DNS vulnerability all about?

The vulnerability is based in servers used by companies to access the internet and handle email. DNS is used by every computer that links to the internet and works similar to a telephone system routing calls to proper numbers, in this case the online numerical addresses of websites. We usually end of using the DNS of the ISP that we use. The vulnerability allows “cache poisoning” attacks that tinker with data stored in computer memory caches that relay internet traffic to its destination. The flaw has existed since 1983 and may well have been exploited without victims noticing. The vulnerability also lets hackers hijack emails and supposedly secure online transactions.

How can we plug this vulnerability?

At the ISP level, they need to add some patches so that their customers are safe. But this threat was announced in July 2008 and if your ISP has not done it so far, then chances are they will not fix it at all.

Thus, at the consumer level, if Doxpara tells you that your ISPs DNS is vulnerabe, then stop using your ISPs DNS and switch to OpenDNS.com.

To learn more, read:

http://www.news.com.au/dailytelegraph/story/0,22049,24141990-5001028,00.html

http://www.doxpara.com/

a. My earlier blog is very very focussed (only allows me to write about my notebook/ technology migration experience). I want to expand the focus to cover other issues that I think about and would like to discuss with others.

b. I hear great things about WordPress and want to give it a try.

c. This blog will be more of a discussion ground with friends (friends ~people who think/ care about similar issues). Am currently trying to work out the design carefully, so as to facilitate the same.