Milestones: Are They Worth Remembering?

Um, yes! They are DEFINITELY worth noting.  At least I think so.  And since I’m writing this post, I think I’ll remember an important milestone for this year: For those who are reading this from my blog, you’ll notice that my Wigle counter has tipped over 10,000 discovered access points.
Is this a Christopher Columbus moment of discovery?  Of course not.  All it indicates is that I live in an affluent area where access points are very prevalent.  Nevertheless, reaching this milestone is important to me.  The number indicates that I’ve found over 10,000 access points during my recent bicycle commuting efforts.  It is a symbol for lots of miles on my bike.  And it implies prestige points in an otherwise invisible ego campaign! 😉
If you think about this mathematically, consider a circle with a radius of about twelve miles.  Since my path is varied (i.e., not just a straight line), I must simplify and say that I ride within a given fraction of the circle.  For further simplification, let’s assume that the slice is roughly an eighth  of the circle’s area.  That means that I’ve found 10K “new” access points in an area of approximately 56 1/2 square miles.  That equates to 176+ access points per square mile.
That doesn’t sound like much.  And it probably isn’t.  But here are the probable reasons that the number is so low:
1) I have probably overestimated the size of my “slice” of the circle. In fact, I guarantee that I have because I ride on roads.  If I were honest, I’d have to say that while I have ridden around an arc that is similar to 1/8 of the overall area, I’ve probably NOT covered that area very thoroughly.  Indeed, the area that I have thorough coverage for may only be a sixty-fourth of the circle’s area.  If I used that number, I’d see 1400+ access points per square mile!
2) There is a lot of unusable (and/or undeveloped) land between home and my office.  So we have a very uneven distribution of houses and businesses.  But we could simplify and assume that we have an evenly distributed population.  If anything, I travel the more populous areas to ensure that I have ample visibility.
Of course, I’m not the only person who has pondered this subject.  In fact, there is an awesome paper (written by Kipp Jones and Ling Liu of Georgia Tech) that talks about some of the issues associated with WiFi density in and around population centers.
And there is an even more impressive article by Luke Driskell (Lousiana State University).  In his article, Mr. Driskell attempts to describe how WiFi density is a solid indicator of differences in the economic makeup of neighborhoods in Baton Rouge, Louisiana.  Of course, there are distinct implications (in Mr. Driskell’s paper) about how public WiFi may bridge some of the economic differences.  But for purposes of my analysis, I just wanted to know whether 176+ access points per square mile is indicative of a lot of access points or simply a few.
So what have I determined?  First, if I want to make conclusions from numbers, I need to be more rigorous.  Second, I need to map my thesis to real demographic data (i.e., neighborhood economic data).  I certainly observed that some of the poorer neighborhoods I ride through have fewer access points.  But if I want to prove the hypothesis, I have to actually posit a real hypothesis – and then rigorously test it.
Since I don’t have time to do that, I’ll just make wild speculations from incomplete studies.  That means I’m either a journalist, a politician or a weird hybrid being from both strains of homo americanus.
So here is the provable claim: I am excited that I have cataloged so many access points.  Have I bested Mr. Dunker yet?  No, I have not.  At least, I haven’t YET.  But I need to approach his numbers slowly – lest he react and overwhelm my meager findings with his larger antenna rig.
So yes, it is about size and it is about numbers!
-Roo

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to Yahoo BuzzAdd to Newsvine

Zombie "Kill of the Week"


There is a time and a place for everything.  This week was the time to upgrade my infrastructure.  I’ve had a wireless router since the beginning of the last decade.  My first WiFi router was a 3Com device.  It supported 802.11b.  My next router(s) was a Linksys WRT54G that supported 802.11g.  So now that the new wireless standard has finally been approved, it was time to upgrade to a device that supported802.11n – or whatever draft specification is currently under review/consideration/implementation.
I tend to be a thoughtful man when it comes to buying technology.  So I considered the following:

  • A desire to stream video content
  • A multimedia infrastructure that used Ethernet connections to the TV, the Blu Ray player, and a game console
  • A room location that did not have Ethernet but needed a wireless Ethernet bridge
  • A need to link the high-speed infrastructure and a low-speed camera infrastructure (featuring an 802.11b access point)
  • My past experience with firmware (which included three years of using DD-WRT)
  • A desire to use open source components wherever possible
  • A need to upgrade my broadband bandwidth to support simultaneous streaming and web browsing
  • A desire to switch ISP’s in order to save some money

This was a daunting list.  And I tried to meet every objective on the list.  I think that I may have succeeded – but not without paying a price.
My first choice was to replace the wireless gear that I had.  So I selected a Buffalo wireless router.  In particular, I chose the Buffalo WZR-HP-G300NH as my new router.  It uses the Atheros chipset for the radio.  So I knew that it would provide the signal coverage that we need.  It also ships from Amazon with DD-WRT.  At the same time, I was tired of running a home-built wireless Ethernet bridge for the entertainment center.  So I also purchased a Buffalo WLI-TX4-AG300N as a replacement bridge.
I installed that infrastructure last weekend.  And it worked flawlessly with my Time Warner cable connection.  But I still needed more bandwidth from my ISP – and I wanted to save a few bucks on my monthly cable expenses.  So on Tuesday, I worked from home while my “cable guy” switched my infrastructure from Time Warner to SureWest.  Why SureWest?  Because we had used them many years ago when they were Everest.  And now that I no longer needed any exclusive content from Time Warner,  it was time to change.
The change was not as simple as I would have liked.  First, SureWest needed to string new cable.  OK, I could live with that.  But then SureWest felt compelled to change the cable modem to a Cisco DPC-3010.  This is a fine device.  And I am sure that SureWest got quite a deal with Cisco.  And I know that the Cisco gear is very manageable for the provider.
But the customer experience was awful.
I went from a 15-30mbs service to something quite a bit less.  Yes, I had contracted for 25mbs.  But my experience (as measured by Speedtest.net and Speakeasy.net) was only about 11-12mbs.  I was horribly disappointed.  Indeed, I felt like the corporate zombies had stolen a good thing and replaced it with something less appetizing.
The cable guy had me test a direct connection between my new cable modem and my PC.  In that configuration, I could get ~25mbs.  Shoot!  That meant the issue was with the router when I put it between the cable modem and my PC.  I expected some performance loss.  But 50% is just plain unacceptable.
So I went off to the forums to seek information – and a little solace.  Based upon recommendations from forum gurus, I updated the router firmware to the latest DD-WRT versions.  I first tried build 16144.  I then moved on to build 16214.   But the results were always the same: I was seeing about a 50% bandwidth loss.
I thought the issue might be the cable modem.  So I contacted both SureWest, their outsourced technical support staff and I even checked with Cisco.  It seems that SureWest will not support any modem except their customized and re-branded Cisco.
Consequently, I had but one alternative: change the router.  But I didn’t want to get rid of my shiny new router.  And it had performed so well before the ISP change.  Therefore, I decided to switch to the default Buffalo firmware before I just swapped the whole thing out.  This meant that I would be abandoning one of my requirements: i.e., using DD-WRT.  But I had to test this in order to really determine where the problem was.
After a few minutes of downloading code and a few minutes of uploading the firmware to the router, I had the new/old Buffalo firmware running on the device.  And what was the result?  I started to see performance approaching 25mbs.  Conclusion: DD-WRT, the Buffalo router and the Cisco DPC-3010 don’t work well together.  It could be any number of things.  And I will still pursue a DD-WRT solution.  But for now, I have met all of my customer requirements – while compromising on one requirement from the infrastructure team.
In order to get what you want, you may need to abandon a well-worn rule or two.  For me, I decided to meet my family’s requirements – and defer my geek requirements.
And what was the first movie I streamed using the new infrastructure?  You guessed it: Zombieland.
-Roo

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to Yahoo BuzzAdd to Newsvine

Zombie “Kill of the Week”

There is a time and a place for everything.  This week was the time to upgrade my infrastructure.  I’ve had a wireless router since the beginning of the last decade.  My first WiFi router was a 3Com device.  It supported 802.11b.  My next router(s) was a Linksys WRT54G that supported 802.11g.  So now that the new wireless standard has finally been approved, it was time to upgrade to a device that supported802.11n – or whatever draft specification is currently under review/consideration/implementation.

I tend to be a thoughtful man when it comes to buying technology.  So I considered the following:

  • A desire to stream video content
  • A multimedia infrastructure that used Ethernet connections to the TV, the Blu Ray player, and a game console
  • A room location that did not have Ethernet but needed a wireless Ethernet bridge
  • A need to link the high-speed infrastructure and a low-speed camera infrastructure (featuring an 802.11b access point)
  • My past experience with firmware (which included three years of using DD-WRT)
  • A desire to use open source components wherever possible
  • A need to upgrade my broadband bandwidth to support simultaneous streaming and web browsing
  • A desire to switch ISP’s in order to save some money

This was a daunting list.  And I tried to meet every objective on the list.  I think that I may have succeeded – but not without paying a price.

My first choice was to replace the wireless gear that I had.  So I selected a Buffalo wireless router.  In particular, I chose the Buffalo WZR-HP-G300NH as my new router.  It uses the Atheros chipset for the radio.  So I knew that it would provide the signal coverage that we need.  It also ships from Amazon with DD-WRT.  At the same time, I was tired of running a home-built wireless Ethernet bridge for the entertainment center.  So I also purchased a Buffalo WLI-TX4-AG300N as a replacement bridge.

I installed that infrastructure last weekend.  And it worked flawlessly with my Time Warner cable connection.  But I still needed more bandwidth from my ISP – and I wanted to save a few bucks on my monthly cable expenses.  So on Tuesday, I worked from home while my “cable guy” switched my infrastructure from Time Warner to SureWest.  Why SureWest?  Because we had used them many years ago when they were Everest.  And now that I no longer needed any exclusive content from Time Warner,  it was time to change.

The change was not as simple as I would have liked.  First, SureWest needed to string new cable.  OK, I could live with that.  But then SureWest felt compelled to change the cable modem to a Cisco DPC-3010.  This is a fine device.  And I am sure that SureWest got quite a deal with Cisco.  And I know that the Cisco gear is very manageable for the provider.

But the customer experience was awful.

I went from a 15-30mbs service to something quite a bit less.  Yes, I had contracted for 25mbs.  But my experience (as measured by Speedtest.net and Speakeasy.net) was only about 11-12mbs.  I was horribly disappointed.  Indeed, I felt like the corporate zombies had stolen a good thing and replaced it with something less appetizing.

The cable guy had me test a direct connection between my new cable modem and my PC.  In that configuration, I could get ~25mbs.  Shoot!  That meant the issue was with the router when I put it between the cable modem and my PC.  I expected some performance loss.  But 50% is just plain unacceptable.

So I went off to the forums to seek information – and a little solace.  Based upon recommendations from forum gurus, I updated the router firmware to the latest DD-WRT versions.  I first tried build 16144.  I then moved on to build 16214.   But the results were always the same: I was seeing about a 50% bandwidth loss.

I thought the issue might be the cable modem.  So I contacted both SureWest, their outsourced technical support staff and I even checked with Cisco.  It seems that SureWest will not support any modem except their customized and re-branded Cisco.

Consequently, I had but one alternative: change the router.  But I didn’t want to get rid of my shiny new router.  And it had performed so well before the ISP change.  Therefore, I decided to switch to the default Buffalo firmware before I just swapped the whole thing out.  This meant that I would be abandoning one of my requirements: i.e., using DD-WRT.  But I had to test this in order to really determine where the problem was.

After a few minutes of downloading code and a few minutes of uploading the firmware to the router, I had the new/old Buffalo firmware running on the device.  And what was the result?  I started to see performance approaching 25mbs.  Conclusion: DD-WRT, the Buffalo router and the Cisco DPC-3010 don’t work well together.  It could be any number of things.  And I will still pursue a DD-WRT solution.  But for now, I have met all of my customer requirements – while compromising on one requirement from the infrastructure team.

In order to get what you want, you may need to abandon a well-worn rule or two.  For me, I decided to meet my family’s requirements – and defer my geek requirements.

And what was the first movie I streamed using the new infrastructure?  You guessed it: Zombieland.

-Roo

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to Yahoo BuzzAdd to Newsvine

I'm Like a Kid at Christmas!

I love Christmas for so many reasons:

  1. Today is a reminder that God is with us.  He emptied himself (Philippians 2) to dwell among us.
  2. Today is a reminder that there is always a home where we belong.  I loved the pastor’s homily last night.  He spoke of the prodigal son.  This really IS the true Christmas story. God allows us to choose a path that leads to ruination.  But He is always waiting for us to return.  And He rushes to meet us upon our return.  The birth of Jesus is testament to God rushing to meet His children.
  3. I really do love the gifting process.  I love buying and making gifts for others.  I am thrilled to see joy as someone opens a surprise or when a deep desire (or unmet need) is realized.
  4. And I love kids at Christmas – cuz I am really a kid at heart.

So when the Christmas hubbub finally began to subside, I decided to give myself a little Christmas cheer: I decided to treat myself to ApeX 1.3.1 for the holidays.  Once I had secured root access, I couldn’t wait very long – and it only took four days for my resolve to waver.  I pulled down Rom Manager, installed a bootstrap recovery tool (i.e., ClockworkMod) and got to work.
The process was oh so simple.  There are dozens of “howto” guides on the Net.  So I won’t reinvent them here.  But I will say that the process is not nearly as daunting as the first few WinMo cookers I deployed a few years ago.  If you are cautious, then you can do this with confidence.    And there is so much assistance that you can obtain.  I won’t be a link farm for these kinds of things – especially as there are legal implications.  But I can say that all you need can be found on Google.
-Roo

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to Yahoo BuzzAdd to Newsvine

I’m Like a Kid at Christmas!

I love Christmas for so many reasons:

  1. Today is a reminder that God is with us.  He emptied himself (Philippians 2) to dwell among us.
  2. Today is a reminder that there is always a home where we belong.  I loved the pastor’s homily last night.  He spoke of the prodigal son.  This really IS the true Christmas story. God allows us to choose a path that leads to ruination.  But He is always waiting for us to return.  And He rushes to meet us upon our return.  The birth of Jesus is testament to God rushing to meet His children.
  3. I really do love the gifting process.  I love buying and making gifts for others.  I am thrilled to see joy as someone opens a surprise or when a deep desire (or unmet need) is realized.
  4. And I love kids at Christmas – cuz I am really a kid at heart.

So when the Christmas hubbub finally began to subside, I decided to give myself a little Christmas cheer: I decided to treat myself to ApeX 1.3.1 for the holidays.  Once I had secured root access, I couldn’t wait very long – and it only took four days for my resolve to waver.  I pulled down Rom Manager, installed a bootstrap recovery tool (i.e., ClockworkMod) and got to work.

The process was oh so simple.  There are dozens of “howto” guides on the Net.  So I won’t reinvent them here.  But I will say that the process is not nearly as daunting as the first few WinMo cookers I deployed a few years ago.  If you are cautious, then you can do this with confidence.    And there is so much assistance that you can obtain.  I won’t be a link farm for these kinds of things – especially as there are legal implications.  But I can say that all you need can be found on Google.

-Roo

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to Yahoo BuzzAdd to Newsvine

Why Root Your Android Phone?

Over the last three months, I have repeatedly told myself that I would not root my Droid 2.  I made this choice because I wanted to use the same kind of phone that the average customer would use.  After ninety days, I am completely satisfied that the “average customer” can have a warm, inviting, robust and feature-complete experience on an Android phone.  And after ninety days, I can also confirm another simple fact: I am not an average customer.
For those who have followed my blog for a while, you will remember that I used custom firmware on a variety of Windows mobile phones.  And you will remember that I have run custom firmware on my broadband router for over seven years.  So many of you have probably taken bets on when I would break down and deploy custom firmware on my Android phone.
Well, I hate to disappoint you.  But I have not yet loaded  a custom ROM onto my Droid 2 – at least, not yet.  But I have rooted my phone.  And I did not take this action lightly.  Before I was willing to forever say goodbye to the safe shores of carrier-based support, I needed to have some concrete reasons for the change.  So here are my reasons:

  • I need to backup my phone.  This includes my customer data, my applications and the system itself.  And my carrier does not provide a means to do this.  So if I want to back up key files on my system, I need to have escalated privileges.
  • I need to control the firewall that is on my phone.  I want to say which apps can use which ports.  And I want to say which external hosts I will allow threw my defenses.  To do this with the builtin firewall (i.e., iptables), I need to have escalated privileges.
  • I need to be able to proxy access for a selected set of applications.  Unfortunately, most Android apps do not use proxy settings.  In the future, I am sure that most good apps will have this feature.  But for now, few have this feature.  So I need a way to “impose” a proxy on apps that I choose.  In short, I need a transparent proxy.  Since I use Privoxy and Orbot, I need to have escalated privileges.
  • I really want to block ads from a number of applications.  I do think that ads are a good way to generate revenue for small software companies.  But if I have paid for an app, I don’t want the adware.  Indeed, I consider some ad services to be real crapware.  So I want to blacklist some ad servers.  To do this, I need to update my local hosts file.  By pointing some of these ad servers to my local loopback, I can negate the nastiness of many of these advertisers.  To do this, I need to have escalated privileges.
  • I really want to control the tunneling tools that I use to connect to my home systems.  I use ssh to tunnel VNC/RDP traffic into my house.  And I need to have full control of these tunnels.  You can use some of these tools in user mode.  But kernel mode tools are much better for some of these core services.  To do this, I need to have escalated privileges.

Should you root your phone?  That one is up to you.  I will take no responsibility for supporting you.  And there is no warranty, either explicit or implicit, when you decide to take control of your phone.
But if you are willing to accept the responsibility to support yourself, there are thousands of people who would be willing to help – including myself.  There are hundreds of sites that can help you on this journey.  But one of the best places is the xda-developers forum.
If you decide to take your first step into a brave new world, good luck on the journey – and I can’t wait to see you on the other side.
-Roo

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to Yahoo BuzzAdd to Newsvine

Not So Seamless – But Oh, So Delicious

Sometimes, you have way too many balls in the air.  I saw the shiny bauble (Tor on my Droid 2) and I had to chase it.  Here is what happened:

  1. I tried to download the tool from the Tor site.  That proved fruitless.  I was connected via 802.11 to my home network.  And my home network has content filtering through a third-party.  And this site was blocked.
  2. Consequently, I had to disconnect from the home network and connect via the 3G network.  The download still had some problems.
  3. So I downloaded to my PC and connected up the USB cable.  From there, I moved and launched the package installer.  The installer did it’s job and Tor was on my phone.
  4. Too bad I couldn’t connect to the Tor network.  I tried the default test site from my Android browser and was greeted with the fact that my browser wasn’t using Tor.  That made some sense as I hadn’t pointed my browser to a local proxy that was configured to use the Tor connection.  Since Orbot uses Privoxy, I had the proxy.  I just had to configure the browser to use the proxy.
  5. Unfortunately, changing the proxy on the default Android browser is not as easy as you might think.  There are plenty of articles about how to update the settings if you have rooted your phone; I have not as I want to see what an average user can do with their phone.  But most articles also said that you could use adb to update the settings.
  6. I went ahead and tried to use adb.  But I had some issues getting adb to work from my PC to my Android phone.  The basic trouble is that I had already change my SDK to support Gingerbread.  And adb was moved in the new SDK to the platform-tools directory.  That one was easy to fix: I just had to change my PATH to include the new directory.
  7. The next attempt was also unsuccessful; I had authorization problems.   Rather than keep stumbling, I turned to “off-the-shelf” solutions to update the proxy setting.
  8. Fortunately, there are plenty of tools in the Android Market to change the proxy settings.  Once I downloaded one of them, I changed my browser’s proxy settings and retried the test that comes within Orbot.  The results of that test are found in the image above.

I’m not done with my tests.  But I am encouraged that I can now encapsulate everything from within a Tor tunnel.  More to follow…
-Roo

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to Yahoo BuzzAdd to Newsvine

It's About Time – In So Many Ways

This week was quite surreal.  I’ve spent almost thirty-five years working with computers.  [Note: That includes a few years as a teenager.]  I’ve built computers from scratch.  I’ve held practically every job you can imagine in the software industry.  But I have never been officially certified in anything.  So I’ve been confronted with one of my own personal boogeymen: I must take a test that I must pass in order to keep my job.  What’s up with that?
I have chaffed at the utter indignity of it all.  And I’ve been more than a little bit apprehensive about the upcoming test.  [Note: I’m taking my test on December 27th.  So I would really appreciate your prayers.]  And I’ve also laughed at the ridiculousness of such tests.  As a senior leader, I recognize the importance of such things.  And as an individual contributor, I recognize the fact that such tests are really poor predictors of performance. But as a man called by God to set an example, I must set any and all of these other considerations aside.  I must prepare as if I were doing this for the Lord – as indeed, I am.  And I must demonstrate my faith with my gentle attitude.   So I am soldiering on.
So after a long week of staring at LCD monitors, I was so glad to get home and just relax. Of course, that didn’t happen.  Things have just kinda stacked up at home.  So I finally got some time to attend to some overdue items.
I finally got my revised taxes submitted to my state’s department of revenue. This is always arduous, frustrating and altogether soul-rending.  But I just needed to set aside a few hours to pull all the pieces together.  Hopefully, the state will understand what I have submitted.  But if they don’t, this will take a whole lot more time to iron out.  But I’ve taken the first few steps in the journey.  So I have a smile on my face.
I also had to assemble all of my ‘dependent’ verification documents for my employer.  BTW, I’ve never had to provide so much data before.  I had to get birth certificates for everyone.  I even had to find my marriage certificate. Unfortunately, the marriage certificate was in a safety deposit box at a bank that I haven’t visited for over twenty year.  Neither Cindy nor I could find the keys for the safety deposit box.  So after paying to have the lock drilled out, we retrieved our marriage certificate.  And we bought a fire box so that we could securely store all of these documents in the house.  As of now, all of the older and newer documents that need to be protected against calamity are now safety tucked away in a hiding place that can survive fires or tornadoes.  With this done, I got all of the ‘dependent’ information bundled together and sent to my employer.
In addition to this, I’ve finally finished all of the retirement consolidations that I’ve been doing over the last few months.  It’s nice to have all of the administration in one place.  And it is good to have my retirement savings properly invested in a diverse number of well-managed funds.  I can’t wait to do my next quarterly review in order to see how well (or poorly) we’ve done with my new plans.  I certainly can’t do any worse than I did when almost everything was vested in (and through) only one corporation.
But these things aren’t what prompted me to write this post.  Yes, all of these things were woefully overdue.  But this morning, I got a chance to ‘geek out’ – just a little.  My classes have focused on information security.  And I have always been an idiot-savant in this area.  I’ve never had any formal training in the subject – even though I was a senior security engineer about twenty-five years ago.  I’ve always learned by doing.  And I have a passing familiarity with the subject.  [Note: If you don’t believe that last statement, just read some of my posts over the years.  You’ll see that I am wholly entranced by security and privacy matters.]
With the purchase of my Android phone, I’ve had to confront a whole lot of privacy issues.  I use my phone to securely connect to my home computers.  To do this, I tunnel VNC through SSH.  I also store some fairly important documents on my phone.  So I use Truecrypt (on my PC) to create and store a secure backup of a small number of important files.
But I’ve always had to encrypt the data myself.  Or I’ve had to use other tools on my phone and/or PC.  Basically, all of these tools were file-oriented solutions.  At the same time, there were very few options to securely encrypt streams of data between the phone and other computers.  Yes, I could use https to build a secure tunnel to the site I was interacting with.  But if I wanted to secure all traffic, I was out of luck – until now.
The folks at the Tor project have released an Android tool named Orbot.  I had a little trouble downloading the tool OTA.  But I finally got it by transferring the package to my SD card.  Over the next few days, I’ll be testing this tool to see how it works.  I am pretty darned psyched that this tool is now available – and it’s about time that phones could participate on the Tor network.

-Roo

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to Yahoo BuzzAdd to Newsvine

It’s About Time – In So Many Ways

This week was quite surreal.  I’ve spent almost thirty-five years working with computers.  [Note: That includes a few years as a teenager.]  I’ve built computers from scratch.  I’ve held practically every job you can imagine in the software industry.  But I have never been officially certified in anything.  So I’ve been confronted with one of my own personal boogeymen: I must take a test that I must pass in order to keep my job.  What’s up with that?

I have chaffed at the utter indignity of it all.  And I’ve been more than a little bit apprehensive about the upcoming test.  [Note: I’m taking my test on December 27th.  So I would really appreciate your prayers.]  And I’ve also laughed at the ridiculousness of such tests.  As a senior leader, I recognize the importance of such things.  And as an individual contributor, I recognize the fact that such tests are really poor predictors of performance. But as a man called by God to set an example, I must set any and all of these other considerations aside.  I must prepare as if I were doing this for the Lord – as indeed, I am.  And I must demonstrate my faith with my gentle attitude.   So I am soldiering on.

So after a long week of staring at LCD monitors, I was so glad to get home and just relax. Of course, that didn’t happen.  Things have just kinda stacked up at home.  So I finally got some time to attend to some overdue items.

I finally got my revised taxes submitted to my state’s department of revenue. This is always arduous, frustrating and altogether soul-rending.  But I just needed to set aside a few hours to pull all the pieces together.  Hopefully, the state will understand what I have submitted.  But if they don’t, this will take a whole lot more time to iron out.  But I’ve taken the first few steps in the journey.  So I have a smile on my face.

I also had to assemble all of my ‘dependent’ verification documents for my employer.  BTW, I’ve never had to provide so much data before.  I had to get birth certificates for everyone.  I even had to find my marriage certificate. Unfortunately, the marriage certificate was in a safety deposit box at a bank that I haven’t visited for over twenty year.  Neither Cindy nor I could find the keys for the safety deposit box.  So after paying to have the lock drilled out, we retrieved our marriage certificate.  And we bought a fire box so that we could securely store all of these documents in the house.  As of now, all of the older and newer documents that need to be protected against calamity are now safety tucked away in a hiding place that can survive fires or tornadoes.  With this done, I got all of the ‘dependent’ information bundled together and sent to my employer.

In addition to this, I’ve finally finished all of the retirement consolidations that I’ve been doing over the last few months.  It’s nice to have all of the administration in one place.  And it is good to have my retirement savings properly invested in a diverse number of well-managed funds.  I can’t wait to do my next quarterly review in order to see how well (or poorly) we’ve done with my new plans.  I certainly can’t do any worse than I did when almost everything was vested in (and through) only one corporation.

But these things aren’t what prompted me to write this post.  Yes, all of these things were woefully overdue.  But this morning, I got a chance to ‘geek out’ – just a little.  My classes have focused on information security.  And I have always been an idiot-savant in this area.  I’ve never had any formal training in the subject – even though I was a senior security engineer about twenty-five years ago.  I’ve always learned by doing.  And I have a passing familiarity with the subject.  [Note: If you don’t believe that last statement, just read some of my posts over the years.  You’ll see that I am wholly entranced by security and privacy matters.]

With the purchase of my Android phone, I’ve had to confront a whole lot of privacy issues.  I use my phone to securely connect to my home computers.  To do this, I tunnel VNC through SSH.  I also store some fairly important documents on my phone.  So I use Truecrypt (on my PC) to create and store a secure backup of a small number of important files.

But I’ve always had to encrypt the data myself.  Or I’ve had to use other tools on my phone and/or PC.  Basically, all of these tools were file-oriented solutions.  At the same time, there were very few options to securely encrypt streams of data between the phone and other computers.  Yes, I could use https to build a secure tunnel to the site I was interacting with.  But if I wanted to secure all traffic, I was out of luck – until now.

The folks at the Tor project have released an Android tool named Orbot.  I had a little trouble downloading the tool OTA.  But I finally got it by transferring the package to my SD card.  Over the next few days, I’ll be testing this tool to see how it works.  I am pretty darned psyched that this tool is now available – and it’s about time that phones could participate on the Tor network.

-Roo

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to Yahoo BuzzAdd to Newsvine

War-strolling With Bailey

One of the biggest blessings each holiday is having all of my kids at home.  And this holiday is no exception.  Bailey was here for almost a week.  And while she spent much of her time with her beau, she also spent time with her father.  And for the past couple of days, she and I have had a chance to stroll through the neighborhood.
Today, we made it a point to go to the neighborhood public library.  And the weather was quite accommodating.  Today, we walked +4 miles.  And we also just chatted.  We chatted about life, about long-term love and about our Savior.  It was quite a refreshing and adult stroll – and I got a chance to walk down some streets that I don’t ride on.
So I took the opportunity to run the Wigle WiFi war-driving app on my Droid 2.  And what to my wondering eyes did appear but a few hundred more access points as we strolled around the neighborhood.
I also got a chance to check out some mapping functions and use some real estate apps (like Zillow).  It’s always good when my location-based tool chest get a little bigger.  But while all of these technologies are very cool, the best part of the stroll was the time that I spent with my daughter.  I am truly blessed to have children that are still willing to talk to me!
-Roo

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to Yahoo BuzzAdd to Newsvine