Subscribe now!
The Latest
Newsletter
Featured Videos
Set up a secure virtual host in Apache
December 22nd, 2008 by Elliot Isaacson in
Setting up an https server in Apache is easy. This tutorial covers how to create and sign your ssl certificate as well as how to configure the web server.
Recently Popular
From the Magazine
January 2009, #177
It's a battle as old as time: good vs. evil. Fortunately, Linux and FOSS are on our side as we wage the battle against those who try to steal our secrets and invade our systems.
Checking your system's security is best done sooner rather than later. Test the locks with our article on security verification; find out how to use PAM to help secure your systems; use MinorFS and AppArmor to implement discretionary access control; learn more about Samba security in part III of our series; use Darknet to help detect bots and secure your systems; use the Yubikey to increase your site's security; and don't forget to lock the doors, because a cold boot attack could render your security useless if somebody has physical access to your computer.
But, we're not just about sowing the seeds of fear. We also show you how to use memcached in Rails, how to manage multiple servers efficiently, how to deploy applications easily with Capistrano, how to manage your videos with MythVideo, how to mix it up a bit (your audio that is), and even play a few games.






Friends dont let friends use proprietary closed protocols
On June 21st, 2008 Jean-Marc Liotier (not verified) says:
Skype is not Free Software : you cannot change it, examine it for errors and security holes, or use it except with their permission and on their terms. You can’t trust your communications to Skype, even if it is convenient and popular.
Skype's protocol is only used by Skype, not published and not implemented by anyone else. You cannot make it interact with anything but the Skype client. You cannot combine it with anything else to make it more valuable. You cannot have a client more suitable for your needs as the official Skype client is the only one allowed.
With hundred of implementations of SIP, IAX and other open protocols; and with E164 and others to identify users, I cannot understand why anyone would use Skype.
Who in their right minds would use a proprietary and closed network ? Just say no ! We, as consumers, are aware of the benefits of an open standards based networks. We have a duty to make the right choices and explain them to the people around us. That begins with telling our contacts that we are not available on AIM, Yahoo, MSN, Skype & co. Interoperability is not enough - only standards and open networks will do !
I know I sound like a an extremist zealot. But this is an important battle. What we have today exists only because TCP/IP, SMTP and other standards prevailed and made the open Internet. The next generation of services depends on an IM system. It may be XMPP, it may be SIP based IMS infrastructures - whatever. But please don't let it be a bunch of closed systems such as Skype.