Public Access Computing: Live CD

My initial encounter with the Ubuntu liveCD (Gnoppix) was not particularly inspiring. The version I used had a refresh rate of 60 Hz for the display that produced images that shimmered to the point that the screen was impossible to look at for any extended period of time. With the screen resolution set to 640*480, and apparently unchangeable, and a low refresh rate, I found images and information that did not fit the screen and a quivering screen that threatened to induce a seizure. After some fiddling around and advice I was able to improve the screen resolution and the refresh rate issue improved. My thought was that for users to be really comfortable with this technology the switch between the Windows operating system and a liveCD version must be a little more seamless.

I proceeded to test the open source live CD with a view to using the PC as if I was in a public library. I would never use a public access terminal to perform tasks such as security-sensitive computer banking and was not inclined to do so with the live CD, so I cannot comment on how easy or difficult that process would have been. I suspect many people do use these terminals in this manner. It would seem that a live CD offers reasonable security for the user unless there was a hardware-based keylogging device attached to the keyboard. Since the Gnoppix live CD makes it unnecessary to start the Windows OS a software based keylogging device would not work.

I performed some basic computing functions on the PC that might be undertaken on a public access computer (PAC). I searched the Web using Firefox, looked at numerous Web sites, grabbed a screenshot, posted to my LIS525 Blog, downloaded files as PDF’s (with the “evince” program) and saved them to my memory key. Since I could not access the FIMS network I could not print the files. I opened and saved files in the Open Word program, checked and sent email through my Gmail account (The load time for Gmail seemed to be fairly long – about 45 seconds – but I am not sure if that was a Gmail problem rather than a Gnoppix problem). I used the “GIMP” open source software to manipulate a graphic image and looked at several other utilities. All were highly satisfactory. Familiarity and name recognition are issues that occurred to me when using the open source software. Will people in a public library setting be comfortable with the slightly different interface? Despite the value of the open source software there is probably a sizeable portion of users who would prefer the Photoshop, Adobe and Microsoft Word programs simply for name recognition.

The reasons for using a PAC in a library are as vast as the reasons for using a computer in the home or office. The library, therefore, must be able to guarantee that the PACs are available on an ongoing basis. That is, they must operate relatively free of breakdowns, over long periods of time, and with different users (Sendze). Constant breakdowns would be expensive for the library because of increased maintenance costs. Also, it would be an inconvenience for the users if there were fewer PACs available. With a live CD operating system the computer would be less likely to be subject to inadvertent alterations by novice or malicious users.

As with more traditional library functions the library’s PAC policies and procedures must be able to ensure user privacy. As has been suggested in class, the possibility of legal action might exist if a library offers services and, as a result of those services, a user has his/her transactions/privacy/passwords compromised. The library must also maintain the integrity of the information contained in the computer system: staff information, OPAC and other library service information. A “terms of use” page where the library can warn patrons against certain uses of the technology and where they can alert patrons to potential risks associated with use of a PAC is helpful. The terms of use contract may provide some measure of security from legal action if acceptance of the terms implies an understanding and acceptance of the risks. However, these instruments are probably no more useful as legal protection than the little warnings printed on the back of hockey tickets that attempt to reduce liability should you be injured by a flying puck.

The live CD seems to offer a reasonable likelihood of a secure computing environment. From the users point of view I would prefer to carry the secure operating system with me, perhaps on a memory key, where I can load my preferences, email and other utilities and not have to worry about what might be on the PC and where my information might be going. To be able to use this technology one would have to be able to reboot the PC. Would libraries be amenable to people doing this to their machines? I tend to believe there would be a great deal of hesitation.

There are numerous commercial resources available to libraries to secure their PACs. CybraryN Solutions , Userful’s DiscoverStation, LockDown Rx by Horizon DataSYS Inc., and Faronics Anti-Executable and Deep Freeze offer security, management and patron authentication software for PACs. The software makers suggest that their products will block “unwanted content access, downloads, and system changes… [And they are] virtually immune to all viruses.” (Userful) However, it occurs to me that anything that suggests that it is “the standard in bulletproof disk protection” is simply inviting a challenge to have their systems hacked. Ubuntu provides the services that the proprietary software sells only it does so free of charge. Ubuntu provides immunity to virtually all viruses without the hassle of looking for and downloading all of the anti-viral fixes and updates that would be necessary for a software solution.

I am a little hesitant, however, to enthusiastically suggest that library IT departments look to switch their proprietary software to open source. The average library user has a comfort level with the name brand software that cannot be overlooked. I am also concerned about the need to work out problems with the open source software. Is the librarian in a small operation equipped to perform these tasks? Are they sufficiently technologically proficient? Ubuntu states that it can provide support services. Is this service available for most other open source materials?

Works Consulted

Moore, S. R. (2001). Libraries to labs: Managing public access computer labs in an academic library environment. The Reference Librarian, (74), 207-220.

Sendze, M. (2006) The battle to secure our public access computers. Computers in Libraries, 26(1), 10-16.

Wayne, R. (2004) An overview of public access software management tools for libraries. Computers in Libraries 24(1) 24-6, 28-30.