Author Archive

Free software.

Have you ever read the EULA that you are presented with when you buy a new computer or piece of software and you are prompted with that “I Agree” checkbox? I’m guessing no. I never have either. You would likely be surprised if you did read it. Here I’m doing a basic compare and contrast between the Windows 7 Ultimate EULA that comes on a new PC and the GPL (Gnu General Public License).

MICROSOFT SOFTWARE LICENSE TERMS
WINDOWS 7 ULTIMATE N

2. INSTALLATION AND USE RIGHTS.
a. One Copy per Computer. The software license is permanently assigned to the computer with
which the software is distributed. That computer is the “licensed computer.”
b. Licensed Computer. You may use the software on up to two processors on the licensed
computer at one time. Unless otherwise provided in these license terms, you may not use the
software on any other computer.
c. Number of Users. Unless otherwise provided in these license terms, only one user may use the
software at a time on the licensed computer.

8. SCOPE OF LICENSE.

The software is licensed, not sold. This agreement only gives you some rights
to use the features included in the software edition you licensed. The manufacturer or installer and
Microsoft reserve all other rights. Unless applicable law gives you more rights despite this limitation,
you may use the software only as expressly permitted in this agreement. In doing so, you must
comply with any technical limitations in the software that only allow you to use it in certain ways. You
may not

· work around any technical limitations in the software;
· reverse engineer, decompile or disassemble the software, except and only to the extent that
applicable law expressly permits, despite this limitation;
· use components of the software to run applications not running on the software;
· make more copies of the software than specified in this agreement or allowed by applicable law,
despite this limitation;
· publish the software for others to copy;
· rent, lease or lend the software; or
· use the software for commercial software hosting services.

26. LIMITATION ON AND EXCLUSION OF DAMAGES.

Except for any refund the manufacturer or installer may provide, you cannot recover any other damages, including consequential, lost profits, special, indirect or incidental damages. This limitation applies to
· anything related to the software, services, content (including code) on third party Internet sites, or third party programs; and
· claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence, or other tort to the extent permitted by applicable law. It also applies even if
· repair, replacement or a refund for the software does not fully compensate you for any losses; or
· Microsoft knew or should have known about the possibility of the damages.

Taken from: http://www.microsoft.com/About/Legal/EN/US/IntellectualProperty/UseTerms/Default.aspx

The Free Software Foundation & The Gnu General Public License

The Foundations of the GPL
Nobody should be restricted by the software they use. There are four freedoms that every user should have:
the freedom to use the software for any purpose,
the freedom to change the software to suit your needs,
the freedom to share the software with your friends and neighbors, and
the freedom to share the changes you make.

Taken from: http://www.gnu.org/licenses/quick-guide-gplv3.html

In the GPL v3 any language devoted to what you may not do with the software is for the purpose of ensuring that the freedoms granted by the license are not infringed. For example, you may not modify it and then license it in a different way.

There is one way in which the GPL and the Microsoft EULA are quite similar. They both provide no real warranty. The GPL is even more absent of warranty as it provides none at all. The MSFT EULA does provide a 90 day warranty for defects.

I have on numerous occasions heard the argument that proprietary software is better if only for the fact that, if it performs poorly or causes damage then there is some recourse against the manufacturer. As paragraph 26 in the MSFT EULA above states, you can see that is not the case.

I suspect that people not familiar with “free as in speech” software have the notion that if it doesn’t cost money then it can’t be good. Those that are familiar understand that is not the case. If you have not had the pleasure to experience free software then you owe it to yourself to give it a try. You can get started with something like The Open Disc .

Be aware that terms are often used that misrepresent the true nature of software licenses. You will hear the term “open source” applied to many software product that may not necessarily be “free as in speech” free. Free software is however inherently open source and this can cause confuision. This is a topic for another discussion but it is good to be aware of it.

FreedomBox project.

I like this. I particularly like the idea of this being able to form a mesh. In my opinion it will be the mesh network that we will eventually rely on for the free dissemination of information. There are many other projects out there that can be aggregated to form the mesh. I mentioned the mesh-potato in the past. There are also many consumer grade wireless routers that can be adapted to the mesh task with freely available custom firmware. I use the WRT54GL and Tomato at home now. Its brilliant.

Here are some other mesh network related sites:

Business FIOS at the office. Part II.

Our changeover from XO DSL for Verizon FiOS is now complete. We just ordered the cancellation of the DSL line yesterday so there is no turning back now. Our network topology with the DSL service was not what I would call ideal, particularly when it came to security and because of that it was quite an effort to get completely functional with the new design. We leased a block of 32 IP’s from the DSL provider and every device on our network had a public Class A address (I know, not cool), it’s just how I did it from the beginning 11 years ago. But I was able to keep everything secure with diligent firewall rules and reviews and by keeping all the systems up top date. I knew long ago that I should change this but it was one of those things that just remained on the back burner.

With the new FiOS package that we chose I went with leasing only 14 IP’s which obviously forced me into making the long needed change. We have approximately 30 network devices here at the office including the IP phones (they were not publicly adressed, thank you). So, logically I did what should have been don in the first place and put all of our network devices on a private network and left only the servers on the public IP’s. Needless to say this required the reconfiguration of all the desktops, printers, the scanner, switches and servers. The switch was the most involved as we had to reassign a number of ports and add an additional VLAN for the new private address network. A number of the servers were also converted to multihomed mode so that they would have a physical connection to both the public and private networks because they provide services to both. Additionally, we have 2 primary DNS servers here that provide name resolution for a number of domains including some that are not ours. The coordination of reconfiguring those servers and making the authoritative record changes was done carefully so as to avoid any downtime for web-services, they were completed on Monday this week.

As I mentioned in the previous post, we are using a Soekris Net5501 as our router and firewall. It runs BSD’s well regarded PF packet filtering software via pfSense and has more than enough processing power to allow our bandwidth to operate at full speed.
net5501_70_bo_front_big_new_1
Our Sonic Wall SOHO 50 is now retired after almost 12 years in service. Proprietary it may have been but it ran like a champ. It’s so out-dated I can’t find a picture of it on the internet. We have the Soekris set up to provide NAT to the new private address LAN and then we set up a bridge from the WAN port to another port that provides the connectivity to all the new FiOS leased public IP’s. Its a mildly complicated configuration but once its going it is rock solid reliable.

I also mentioned in the earlier post that I was looking forward to the speed increase that would allow us to do offsite backups in a reasonable amount of time. That is working out great. We have about 330GB of current and archived data. It wouldn’t pay to start the offsite transfer from scratch so I made an initial transfer at the office and then took that drive to the offsite location. From then on all that needs to happen is to transfer the incremental updates. That amounts to a few GB at most a on any given day, only mere minutes now instead of hours.

It’s done.

Behold the Qube.

Back in the late 90’s when the WWW and the “Information Superhighway” were all over the news and everyone was getting an email address (remember Compuserve and Earthlink and AOL), Linux was also gaining traction because it provided so much of the back-end to the internet. A small group of engineers put their heads together and started the Cobalt company. Their history is available here. Their first product called the Qube 2700 shipped in March of 1998. It was soon upgraded to the Qube 2 and then later the the Cache Qube and Qube 3. There were also a few other products developed for the datacenter/ISP industry, those were the CacheRaq the NasRaq and a series of other Raq* devices. These were all 1U form factor, low power, low cost, rack ready appliances that allowed fast deployment of ISP type services to customers.

I can’t find the original order so I don’t know the exact date but I think it was around late 1999 that I ordered the Qube2. I have always enjoyed tech-gadgets and computers and I just loved these things from the moment I saw one. I set it up at the office in Hackensack where it was connected to our wicked-fast 768Kbps DSL line (now we have 25/25Mbps Fiber). It really had to be the coolest computer you could buy at the time, with its deep cobalt blue case and green Cylon style LED on the front and its diminutive footprint. And best of all it ran Linux. And second best of all it had an unusual 64bit 250Mhz MIPSel processor inside. It really was unique and so much fun to look at and use. I have a soft spot for that one too because it ran our hx4.com site for years.

Cobalt Qube 2
Cobalt Qube 2
Cobalt Qube 2

I still have that Qube2 and two others that I have since obtained through eBay over the last 10 years. The most recent of which was practically a steal (for a fanboy). I was fortunate to happen upon an auction for a NIB Qube2 model in its original packaging, unopened plastic seal on the Qube2 and all the accessories and the original product sticker still intact on the box, all for $33.00. I’m still stoked about it.

IMG_20110224_122153IMG_20110224_122510IMG_20110224_122342

Unfortunately these are obsolete and not good for much other that to serve as neat looking bookends and as conversation pieces. They indeed do still run and there is a community of enthusiasts as you can see from the links above. I have installed NetBSD 5.1 on two of them and that at least makes them current as far as the operating system goes but they are doggedly slow by todays standards and it can get tiresome trying to do anything productive on them. At this point I couldn’t see one serving much purpose other than perhaps for running a persistent instance of IRSSI under Gnu/screen or something similar. One of these days I think I will attempt to gut one of them and stuff a Nano/ITX system inside that will have all the comforts of modern hardware. They still look amazingly current.

Todays funny.

I came across a website related to open code and information freedom and encountered this bio on one of the members of the organization. I’ve redacted their name because I don’t mean to poke fun at them personally. I just thought the bio was pretty funny in a what the heck does that even mean sort of way.

*REDACTED* is a strategic and conceptual advisor to *REDACTED*, helping to articulate an approach toward creative visualization and to evaluate and develop potential partners and engagements relative to that vision. *REDACTED* is a highly regarded experience designer and conceptual strategist, guiding the creative direction and vision of multiple successful endeavors

Motorcycle trip 2005

I know it’s not as exciting as current events but like I mentioned previously, it is therapeutic for me to reminisce on these trips during the cold and icy winter months.

This one was from back in May of 2005. We began in Las Vegas again and headed to the Grand Canyon, we then went through Bryce Canyon and Arches NP. We spent a good deal of time on Southern Utah. Utah is spectacular. There were times we went from high elevation covered in snow caps to lush green valleys and farmland to such striking desert landscapes that made me feel like we were on the moon. One evening we had a great dinner at Rays Tavern in Green River and decided to press on to Moab to stay the night there. Then once we got to Moab we had a miserable time trying to get a place to stay for the night because the entire town was booked with a 4×4 rally. We finally found a room at the Red Cliffs Lodge about 20mi north of town well after 1:00am. The drive up to the lodge was daunting, in the pitch dark on a twisty valley road, it was cool and there was a sense that the river was at our side the entire time but we couldn’t see it. It would have been a nice place to spend some time. We woke up to a fantastic view of the red cliffs on one side and the Colorado River in full spring swell outside our back door. I remember having a great breakfast in the old town jailhouse (Jailhouse Cafe) in Moab then heading to Arches NP. This trip will always stick in my mind out for the surprising beauty and landscape variety that Utah offered and the fact that we had perfect weather the whole time.

2005 TRIP SLIDESHOW

Motorcycle Trip 2008

My good friend Mike Brown and I have done a number of motorcycle trips together in years past. This is the time of year that I reflect on those experiences and gain some escape from the cold and snow here in the north east. They were all trips of a lifetime. I will attempt to get them all posted here eventually. This post highlights the trip from 2008.

These are some memories of our trip from 2008 which took us through the Grand Canyon, Telluride Colorado, Southern Utah and Lake Powell, the White Mountain Apache Reservation in Arizona and Past the VLA in New Mexico.

We hit quite a snowstorm atop the pass from Show Low to Globe in AZ., the kind where you know your fate is no longer in your hands. I don’t know how we made it.

2008 TRIP SLIDESHOW

SSH usage, multiple private keys.

There is no doubt that SSH stands as one of the greatest system administration tools ever. I use it many times a day manually and many more through scripts for sysadmin stuff. Sometimes, like today I needed to do something that I have never needed to do before. And of course SSH is capable.

Due to a new network topology at the office I needed to be able to have SSH source more that one private key for authenticating to a remote host. There is more that one way to do this. I used the first solution as it was the most basic.

In the ~/.ssh folder create a file named “config” and chmod it to 600. Add the following line: “IdentityFile ~/.ssh/id_rsa.keyA” and add a subsequent line for the other private keys you want to use. For example you can have “id_rsa.keyA” “id_rsa.keyB” and so on. Make sure that those references actually match the names of your private keyfiles, if not, rename them. Thats it. From now on, when you attempt an ssh key exchange, all those keys will be sourced.

The second solution is more refined. This is what your ~/.ssh/config file might look like for this method.
Host *.home
IdentityFile ~/.ssh/id_rsa.home
Host *.office
IdentityFile ~/.ssh/id_rsa.office
Host *.wan
IdentityFile ~/.ssh/id_rsa.wan

In this case the host you are connecting to will determine the key that will be presented rather than presenting all keys like the first example.

Thanks to Karanbir Singh and his post for helping me with this.

Vocabulary for the week.

New IP Addresses may crush the earth.

There are  232 = 4,294,967,296 (4.3 billion) IP addresses available in the current IPv4 addressing scheme. The new 128 bit IPv6 scheme offers 2128 = 340,282,366,920,938,463,463,374,607,431,768,211,456. Thats 340 trillion trillion trillion addresses. An impressive number visually, almost unimaginable. Imagine this, if one IPv6 address weighed one 1g then all of them would weigh the equivalent of 56 billion Earths.

I’m going on record and saying that this is going to be enough, forever.