Dave's Tech Blog
A Third Eye on Technology

Imagine you had a computer small enough to fit in your pocket but had the ability to plug it into a computer monitor or HDTV?  Very soon you’ll be able to do just that.  Check this video out to see what I’m talking about.  All he does is take his phone which is running Ubuntu Linux and places it in a dock that’s connected to a LCD monitor, keyboard and mouse.  And like that, he’s got a fully functioning “desktop” PC running right from his phone.  Very cool.

I recently bumped into someone who is a big fan of Skype and uses it to save money at his businesses, as land-lines cost far more for businesses than they do residential customers. He’s seen real savings by using it and was wanting to migrate his company completely away from the local telephone services and go 100% Skype. One of the hitches here was the necessity to have a fax line that you could send and receive faxes on.

Unfortunately there is no good way to send a fax from your computer using Skype. The audio compression that takes place when sound is transmitted from one side to the other undergoes a great deal of detail loss, and this results in error correction protocols taking over and throttling the speed of the fax modem down to a crawl. So in theory, you could use Skype somehow to send a fax but it would literally take forever.

Enter in online faxing services. These are companies that allow you to send and receive faxes over the Internet. In doing some research to find one that performed well and at a modest price I stumbled across someone recommending a company called PamFax.  It was not long after first trying their service that I was pretty sure I could close the book on this egg hunt.

PamFax is delivered to you as a small program you install on your system and use to create your account.  They offer a free membership program which allows you to send three pages for free to see if you like their product or not.  I decided to sign up for the free account and then used a nearby fax machine where I work to send a fax to my new PamFax number.  The instant the fax was sent my PamFax account page auto-updated itself to tell me I had received a new fax.  Faxes are put into an inbox, just like emails, and each fax is downloadable in PDF format.

Sending a fax is also very easy.  You can either use the PamFax program to upload files you want to send or use the virtual PamFax printer device to send your documents to PamFax when you press Print in any application.  Here’s a video that demonstrates how easy it is to send a Fax:

Of course there will be times when you need to fax a physical document that’s already on paper.  The best way to do that is use a flatbed scanner to scan the documents into a PDF file.  You can do this very quickly with any number of Scanner-to-PDF style programs and any scanner.  A free one I’ve found to work well is aptly called Scan to PDF by Ironfist Software.  It is a free utility that you can use to scan multiple pages and then save all of them as one PDF file, which you’d then upload to PamFax for faxing to one or multiple recipients.

The cost for sending a fax varies based on whether or not you want to pay a monthly fee.  If you don’t pay a monthly fee it will cost you 13 cents per page sent and you will not be able to receive faxes.  If you step it up to the “Basic” package you will be able to receive unlimited faxes at a monthly rate of $5.84 plus 13 cents per page sent.  The professional package costs $8.80 a month, includes 20 free page out per month (9 cents per page after that), allows you to keep your received faxes online forever, and gives you the ability to administrate employee access to the account and regulate their limitations.  So there’s something for everybody.

In the end I was pretty impressed with how easy it was to install and use PamFax.  What’s even more impressive to me is their support for Linux. It’s rare that I have to send a fax but the next time I need to I know exactly what I’m going to use.  Good bye Kinko’s!

I’ve recorded a new screencast introducing Ubuntu 10.10. This video gives beginner Ubuntu users a brief tour of the operating system, and covers installing updates, proprietary drivers, customizing appearance, and installing software via the Ubuntu Software Center as well as with downloaded *.deb files, all in less than 10 minutes.  Enjoy!

Back to regular font land now, I just wanted to add instructions for Windows and Ubuntu users on how to install this font.

If you are a Windows user, all you have to do is copy the TTF file into your c:\windows\fonts folder and that should be it.

If you use Ubuntu, save the file to your desktop.  Then right-click on it and click “Open With Font Viewer”.  This will pop up:

Unlike my window, yours will have a “Install” button in the lower right corner for you to click on.  Just click Install and you’re all done.

gksu nautilus /usr/share/fonts/truetype

This tutorial will show you how to share a folder in Ubuntu with a Windows virtual machine running inside Virtualbox. Make the video full-screen to enjoy it in HD quality.

I was just browsing Ubuntu Forums recently and someone wanted to get a second opinion to see if it were indeed true that Linux doesn’t need anti-virus software.  I humbly obliged them with my own answer on the matter:

You don’t need anti-virus for Linux. Others in here will do a better job at explaining why this is, but in short, the OS has a big advantage here due to it being open source. The operating system is a product of crowd-sourcing, much in the same way as Wikipedia has been since it first showed up several years ago. And much like the highly-moderated articles of Wikipedia that require membership and an approval process for changes made to locked articles, so to is a strict moderation that goes on with the source code for Linux before it’s allowed to become part of the official distribution. Everybody is out to identify possible flaws or weaknesses or bugs in the source code and it’s much easier for any single person to make a contribution because the OS and much of the software that runs on it is open-source.

In Windows, the users don’t have the luxury of being able to dig through the source code to look for flaws. All they can do is report symptoms of problems to Microsoft, and the limited number of paid programmers that do have access to the source code then have to decide what flaws are the most important and which ones don’t merit their attention. So with Windows, a bug that affects only 500 people won’t be as important as a bug that affects 500,000 and probably won’t be fixed at all. But if it were Linux and if just one or two of those 500 people were a programmer who had access to the source code and figured out how to fix the problem on their own, the other 498 would actually stand to benefit from a patch that ends up being released thanks to the work of that one developer who had some spare time on his hands and decided to do something about a bug simply because he could.

So throughout the long life of Linux there has been this much more diversified, seasoned, multi-cultured source for development feedback that has helped to make it a much stronger, more “mature” operating system, especially in terms of the way security was designed. If there was ever a person out there who found a way to circumvent that security, there is at least one other who knows exactly how to repair the flaw. The reason viruses are able to best Windows is because their developers can only patch so many holes, and the ones they don’t have time to get around to end up being exploited the most. Third-party software developers that make Anti-Virus software make a killing because Microsoft is unable to handle this responsibility all by themselves, and even still, the best anti-virus software isn’t perfect.

The reason anti-virus software isn’t necessary in Linux is simply because the OS and its updates that patch vulnerabilities do the exact job anti-virus software in Windows is meant for: Prevent unwanted, malicious software or network activity from compromising the system. If there were a flaw in Linux found that allowed something like that, it wouldn’t be the job of some third-party software to safeguard the user against but the job of the OS itself. The reason anti-virus software even exists is simply because Microsoft is unable to handle the immense work load of patching their own source code as well as a crowd of Linux geeks can.

Am I saying Linux is perfect and invincible to viruses? Might it become more susceptible to viruses in the future if it were to ever become as popular as Windows is today? I would think that with an increase in the number of users would also come a complimentary increase in the number of clever developers that would only help to increase the number of eyes available to find flaws and fix them. Saying that Linux would get a lot of viruses down the road because more people are going to use it is like saying Wikipedia will become rife with widespread, uncontrollable vandalism because more people visit it. It hasn’t happened yet, and very likely never will happen because of the way it is designed, moderated and improved upon by the hive mind.

EDIT to add: As mentioned in the first comments below, I failed to acknowledge that while Linux is more robust in the area of security, nothing can compensate for the weakest link in this arrangement:  The User.  A novice user could easily be enticed by a sinister website  that tells them to download a deb file which might contain malicious code and absentmindedly install it or execute a destructive command from the terminal window because they didn’t know any better (like rm -rf ~/*).  Fortunately for novice users there is little if any need to actually venture out into uncharted territory like a terminal window or strange websites to get software, thanks to the official repositories that contain a HUGE collection of software which continues to grow.  I’ve even heard you will soon be able to purchase proprietary Linux-based software through it.  Unfortunately, little can really be done to compensate for user negligence, and trying to compensate for all possibilities would likely result in too many annoying alerts and prompts for the average user (like when Windows Vista sprang the UAC on its users).

There are only a couple of circumstances that I believe anti-virus software on a Linux platform would might be worth having which involve helping to protect other Windows systems.  Say you got an email from someone that contained a virus but you never knew it was there and forwarded it onto someone else who uses Windows, resulting in their day being ruined and you being blamed.  So that’s one scenario.  You might also have a Linux server administrating a network of Windows based workstations which you have read/write access to and use the server to conduct scans of these machines over the network, but at the expense of finite network bandwidth and CPU cycles on the server.

All good things come to an end…  Fortunately, Virtual Dave isn’t one of them.  I’ve recently made the decision to drop my own remote assistance software in favor of using a new open-source VNC launcher called Gitso.  This launcher has a few benefits over the previous iterations of my older “Virtual Dave” software:

• Lightweight:  It’s written in Python and loads very fast.
• Simple:  Sometimes losing a couple “bells and whistles” is a good thing.
• Multiple platforms:  Gitso works on Windows, Ubuntu Linux and Mac OS X.
• Active Development Pipeline:  A feature request I submitted was approved for the next version less than a half hour after I submitted it.
• Open-Source:  Free as in freedom.

There are a lot of features in the coming versions of this software I have been looking for in a VNC tool for a long time.  And who knows, I might learn a thing or two about programming in Python with this little tool.

DISCLAIMER:  Something’s broke with the latest version of Ubuntu (11.10) and adjusting these settings as shown below don’t seem to work like they’re supposed to, and I’ve not yet found a work around.  So this guide may not work at all for you.  I will update it as news emerges about this.

——

VNC is the default remote-desktop protocol for Ubuntu Linux and it can be used by anyone to access their home PC while they are away from home.  Anyone who has used VNC and also has a router are likely familiar with setting up a port-forward rule in their router so that all inbound traffic destined for port number 5900 is sent to the correct/desired PC.  But what if you wanted to be able to do this with multiple PCs on a home network and not have to relay through one PC in order to access another one?

You can do this by setting Ubuntu’s default VNC server (vino) to listen on an alternative port number.  Up until recently, changing this port number was as easy as clicking on an Advanced tab in your Remote Desktop preferences window.  For some reason, this new panel was removed after a more recent update so changing this port number became a bit of a mystery.

I’ve not done any hard digging to find out why this panel was removed, but my guess is they actually rolled the version of vino back to something older to temporarily avoid a known bug encountered with vino on servers that had Compiz enabled.  I’m sure they’ll get it fixed eventually.

In the mean time, this setting is still easy to change if you know where to go.   Here’s what you need to do:

1. Open your Gnome Configuration Editor.  You can do this quickly by pressing Alt-F2, then typing gconf-editor into the box and pressing Enter.
2. In the editor, click Desktop>Gnome>Remote Access.

Once you get to this point, you’ll notice several VNC related settings on the right half of the Gnome Configuration Editor window.  Edit the mentioned values as follows:

alternative_port: In the line that says “Alternative Port” near the top double-click the 5900 to edit and change it to the desired port number you’d like to use.  After you’ve changed this,  right-click on this value again to make a pop-out menu appear and then click “Set As Default”.

authentication_methods:  This value should say (or mention) “[vnc]“.  It might say [none] and that’s okay, but you still need to add “vnc”, so double-click on the value to bring up an edit window and click the Add button.  It will ask you to supply a name/value, so just type in “vnc” (no quotes) and press enter.   You’ll end up with a value of [none,vnc].  I don’t know if it matters or not, but at this point I edited the values further so that vnc was listed above none, so it ended up looking like [vnc,none] in the end.  My thinking behind this has to do with the way some blacklists (TCP/IP for example) delimit their endings.  That’s a whole other blog post…

enabled: There is a solitary check box by this parameter.  Make sure its box has a check-mark inside of it.

use_alternative_port:  Also make sure this parameter has a check mark in it’s box as well.  Also, right-click on this value and then click “Set as Default” for it as well.

Now close Gnome Configuration Editor.

That’s it!  Restart the computer to get the settings to take effect.

You should also do one or more of the following:

• Use Firestarter to add a rule allowing inbound traffic on the new port number you specified above so that your host firewall doesn’t block it.  (Click Applications>Add/Remove and search for Firestarter to install it if you don’t have it already).
• Set a new port-forwarding filter up in your router to direct inbound traffic on that new port towards the PC you just modified (duh!)

To connect to a VNC server on an alternative port, you just add a colon and the new port number to the end of the host address.  Lets pretend the new number if 5901 instead of 5900.  You would type the host address like this:

• 192.168.1.10:5901
• dyndnshostname.homeip.net:5901
• ubuntu.local:5901
• I’ve also used a 1 instead of 5901 and it works.  For 5902 you could probably use just the number 2 by itself, and so on.

And that’s all there is to it!

Every now and then I post questions on www.techguy.org when I’m having difficultly with something computer/networking related.  It was a good place to get your feet wet when aspiring to become a grade A guru and occasionally pull your hair out if you wanted to get into a civil debate with someone about politics.

Recently, I posted the following in their Networking forum:

I have a new Linksys/Cisco router WRT54G2 v.1 with the latest firmware installed. I currently use port forwarding for things like VNC and SSH into my home PC. However, every time I try to set a new rule (for both TCP and UDP) up for bittorrent, the bittorrent clients I try say the port is closed. I’m using an Ubuntu Linux system, and both Transmission and Deluge will say the ports I select are closed, even if I change the port numbers and do another test. So I’m just wondering if anyone has encountered anything like this before and might have an idea of what could be causing this problem.

The thread was alive for a matter of seconds before a moderator locked the thread and replied with the following:

Please read the rules. We will not help with P2P apps.

I was surprised to see this happen, and that’s probably because I use www.ubuntuforums.org more often than any other forum for technical assistance.  Linux people like me approach the controversial topic of bittorrent a little differently…  I decided to send the moderator a private message to let him know what I thought about his decision:

Sorry for violating the rules. However, I would argue that I did not ask a question pertaining to P2P applications at all but a question strictly about networking problems with a Linksys router. I should also remind you that bittorrent is a common protocol used for the transfer of free, non-copyrighted information spanning from GPL licensed open-source software to free music or movies released under the creative-commons license, which is becoming more popular. There is nothing inherently illegal about using bittorrent (the protocol), but it would seem the moderators of techguy.org hold a contrary consensus that I feel they should consider revising in recognition of the legitimate and legal uses of bittorrent.

The above comment and any replies received in any form will be posted publicly on my blog. Thank you for your time.

I got a reply fairly fast.  Here’s what it said:

We cannot and will not assist in the illegal downloading of software through P2P applications, and that includes any impediments offered by networking components to such downloading. Any legal uses of such software are few and will unfortunately need to be included in this prohibition.

The policy has been in place for quite some time now and will not be changed.

Thank you for your concern,
Elvandil

I like his use of the word “prohibition”; like bittorrent is some sort of drug paraphernalia.  I also noticed Mr. Elvandil happens to be Microsoft MVP and a die-hard Windows user who is probably adverse to anything of value that isn’t proprietary.  This is just my own opinion as he is ignoring the fact that millions of people use Linux and a large portion of us download and share our Linux ISO files (for burning to CD) via bittorrent, among many other things 100% legal to share.  It is a world he is unfamiliar with or in denial about.

Fortunately in the world of Linux it’s recognized that bittorrent itself is not illegal at all and I was glad to see a helpful reply in ubuntuforums.org within minutes; a reply that made me realize that sometimes I can be a completely narrow-minded person, too.  ”Did you check your host-firewall?”  Why… NO!    So I opened my firewall manager Firestarter and sure enough saw blocked events taking place on the port I told my bittorrent client and router to use.  All I had to do with allow inbound traffic to take place on that port.  Talk about overlooking the obvious!

(Special thanks to this blog post for showing me how to get this working finally).

About 2 months ago or so I read the tutorial in the above link to help get my fingerprint sensor setup in Ubuntu.  The problem was that it left one simple instruction out:  Paste a line of  text AT THE TOP of a config file (and not at the bottom like I did).  The mistake has been corrected and I’m happy to say my finger print sensor is working in Ubuntu 9.04.  Based on the directions from the the link above, here’s how to set it up (these instructions are meant for version 9.04; see the above link for instructions for 8.04 and 8.10):

Step 1: Click Applications>Accessories>Terminal and paste in the following command:

sudo apt-get update && sudo apt-get install aes2501-wy fprint-demo libfprint0 libpam-fprint

Step 2: Still in Terminal, paste in the following text:

sudo gedit /etc/pam.d/common-auth

This will open a text file called common-auth in Gnome Text Editor.  (Here’s where I screwed up last time).

Step 3: If you want to use both the password and the fingerprint to authenticate (more secure) add at the bottom:

auth required pam_fprint.so

If you want to use either the fingerprint or the password to authenticate (i.e. completely bypass the password through the fingerprint) the following string must be placed at the top of the file:

auth sufficient pam_fprint.so

Once pasted, save and close the file.

Step 4: Press Alt-F2, type “fprint_demo” without the quotes and press enter.

This will launch the fingerprint utility that you can use to enroll the finger you wish to use for future authentications.

That’s basically it.  Special notes:

• If you happen to screw something up in the config file by mistake and lock yourself out of your PC by accident, you can boot into Recovery Mode from the GRUB boot menu to access a root command prompt and edit the above config file using nano (nano /etc/pam.d/common-auth).
• Not all login screens are compatible with this feature.
• To test your finger print in fprint_demo, click on the verify tab at the top and use the verify button to compare an enrolled fingerprint to another finger (or the same finger) and you’ll see the difference.

As of Ubuntu 9.04, I’ve noticed the following quirks:

• Often you will not see an on-screen prompt asking you to swipe your finger across the sensor if the system is waiting for it.  Examples include the login screen, running Update Manager or Synaptic Package Manager, and otherwise most other programs that required your password to run them.
• The only actual on-screen requests I’ve seen so far is when you are unlocking a screen-saver, or are running a program with sudo privileges in a terminal window.