Does any one know if the Evolution will work with Microsoft Exchange Server 2007? Iâ€™ve client and she needs to connect to corporate Microsoft Exchange Server 2007. The problem is – connectivity doesnâ€™t work. If anyone has any information or workaround please comment back.
Update 31/Dec/2007: Rocky pointed me to a thread about MAPI based plugin. It claims to works with Exchange server 2007.
The motto of this site is learn with pictures, not words:
In Pictures tutorials began as part of a research study we conducted for the U.S. Department of Education. The goal: to make it easier for people with learning disabilities to learn computer subjects.
As part of the study, we created simple, illustration-based tutorials. Everyone who tested them–not just people with learning disabilities–said the new tutorials enabled them to learn faster and easier than conventional text-heavy books.
The site offers tutorials on common Linux web programming subject:
Great work! (Thanks to [email protected] for a hat tip)
Version 3 of the GNU General Public License will soon on the horizon. Richard Stallman the father of GPL, GNU project and FOSS activist / hacker recently explained why you should upgrade from GPL 2 to GPL3:
First of all, it is important to note that upgrading is a choice. GPL version 2 will remain a valid license, and no disaster will happen if some programs remain under GPLv2 while others advance to GPLv3. These two licenses are incompatible, but that isn’t a serious problem.
When we say that GPLv2 and GPLv3 are incompatible, it means there is no legal way to combine code under GPLv2 with code under GPLv3 in a single program. This is because both GPLv2 and GPLv3 are copyleft licenses: each of them says, â€œIf you include code under this license in a larger program, the larger program must be under this license too.â€ There is no way to make them compatible. We could add a GPLv2-compatibility clause to GPLv3, but it wouldn’t do the job, because GPLv2 would need a similar clause.
Why Upgrade to GPL Version 3
Recently I received an interesting question from one my regular reader:
What is the basic and important difference between password and passphrase when implementing SSH with DSA/RAS public key authentication? Which one is recommended for daily usage?
The main and basic difference is that you can use multi string phrase including spaces and tabs using a passphrase under ssh. Normal /etc/shadow password is a single string password and many application will breaks with spaces and tabs while using authentication. So your account password must be a single word/string.
For example my account password can be iF33%gNCyzDy
I could create a passphrase: Th1s 1s A t3sT and s3cur3 pa$$phra$3
The advantage is simple you can use spaces and tabs to create a more secure and hard to break authentication method. This makes dictionary based attack quite difficult.
Passwords vs. Pass Phrases
The Great Debates: Pass Phrases vs. Passwords. Part 1 of 3
If anyone aware of more differences please add in comments section 🙂