Getting Email Headers From Outlook
Tuesday, 31. January 2023
Monday, 21. July 2014
In the circles I run in, you can’t go 15 minutes into a conversation without someone bring up Network Neutrality. In my world, it’s a huge deal. And, in my world, there are people on both sides of the issue. If you don’t know what Network Neutrality is, then just pop open your favorite search engine, and type in ‘network neutrality’. You’ll find tons of articles and videos about the subject. All of them asking you to write your elected official, or sign a digital petition. The problem is, for the most part, no one really cares. Sure, there’s a small group of technology people that consider Network Neutrality as one of the most pressing issues of our age, but for the most part, regular folks aren’t getting the message. With so much info available about Network Neutrality from both sides of the issue, you would think people would be all over it.
Wednesday, 9. April 2014
The Heartbleed bug was caused by a programming error in a software package called OpenSSL. This error had the potential of allowing bad people to attach to secure web and email servers, as well as services that rely on the TLS/SSL protocol, and steal the private encryption key off the servers. The TLS/SSL protocol is what puts the pretty little lock in the address bar in your browser. The private key is what the owners of the sites you go to are suppose to keep secret, and not share with anyone because if someone has it, they can decrypt the encrypted data traveling between your system and the server. THIS IS BAD…
The Heartbleed bug was caused by a programming error in the OpenSSLÂ library that deals with TLS handshakes. A couple years back, a new RFC (rfc 6520) proposed a new extension to the TLS protocol that would allow a heartbeat to be exchanged between the client and server to reduce the number of re-negotiations during a TLS session. This all sounds good, and actually is a very beneficial to the protocol in general, but when it was implemented in OpenSSL, an error in the way the code was written allowed a request to grab a bunch of data without checking the boundaries of the data itself. This could allow someone to make a request crafted in a certain way that would cause OpenSSL to return 64k of protected memory data possibly containing the SSL private key of the server.
Wednesday, 17. April 2013
Two weeks ago I thought to myself ‘Gee, now that Samba 4 has a real release out, wouldn’t it be fun to test it out and see how it holds up?‘ And so my adventure began. Now mind you, I’m not a novice to Samba, or to Active Directory, so I figured this would be a simple setup and test. How hard could it be?
Friday, 1. March 2013
Wednesday, 16. January 2013
Saturday, 12. January 2013
Tuesday, 29. May 2012
Seems like most of my job now a days is looking at large systems and isolating problem areas. Things like performance problems, data corruption, or even failure analysis. Many of these systems have several independently managed processes, all tied together in a single forward facing application. Over the years, I’ve developed some methods of approaching system failures and problems that gives me a better chance of quickly evaluating and repairing the issues that plague these systems. I used to believe that these methods were only valid on larger system models, then, one day, a colleague of mine and I were sitting in a small coffee house discussing a problem they were having with one of the desktops they manage. While we exchanged ideas, I suddenly realized that I was using the same mental process on this little desktop as I did with the large cluster systems.
Monday, 1. August 2011
Some of the early groups of articles I penned on this blog, were comparisons of Open Source Groupware projects. At that time, the only one I could really recommend was eGroupware. Although I still believe eGroupware is a valid contender for your Groupware server, I have discovered a project, that in my opinion is leaps and bounds ahead of the pack. The project is called SOGo.