Editing Meeting-20130209
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 24: | Line 24: | ||
'''Presentation: Build Your Own Certificate Authority Using xca''' | '''Presentation: Build Your Own Certificate Authority Using xca''' | ||
− | + | Presenter: [[User:Patbarron|Pat Barron]] | |
There are a number of instances where a system administrator may wish to use certificate-based encryption to for security, to prevent spying on network traffic (for instance, running your own web server that is secured using HTTPS, so that web traffic is encrypted before being sent over the network), or to implement client authentication for something like a VPN. This generally requires that a Certificate Authority (CA) issue certificates for your use - you might choose to use self-signed certificates instead, but this will result in dire security warnings from web browsers about certificates issued by an "untrusted issuer", and some things won't allow you to use self-signed certificates at all. But why pay a recognized CA to issue certificates for you, that are probably going to be used by no one other than yourself and possibly your friends, and which don't need to be trusted by the general public? | There are a number of instances where a system administrator may wish to use certificate-based encryption to for security, to prevent spying on network traffic (for instance, running your own web server that is secured using HTTPS, so that web traffic is encrypted before being sent over the network), or to implement client authentication for something like a VPN. This generally requires that a Certificate Authority (CA) issue certificates for your use - you might choose to use self-signed certificates instead, but this will result in dire security warnings from web browsers about certificates issued by an "untrusted issuer", and some things won't allow you to use self-signed certificates at all. But why pay a recognized CA to issue certificates for you, that are probably going to be used by no one other than yourself and possibly your friends, and which don't need to be trusted by the general public? | ||
Line 36: | Line 36: | ||
'''Presentation: The Rise and Fall of the WebOS Mobile Operating System''' | '''Presentation: The Rise and Fall of the WebOS Mobile Operating System''' | ||
− | + | Presenter: [[User:Centinel|Justin Smith]] | |
"In the span of just three years, webOS went from being a media darling to a running gag. What happened? How did it | "In the span of just three years, webOS went from being a media darling to a running gag. What happened? How did it | ||
Line 43: | Line 43: | ||
'''"Hot Seat" Discussion Event: Open Source License Smackdown!''' | '''"Hot Seat" Discussion Event: Open Source License Smackdown!''' | ||
− | |||
We're going to put the names of 6 open source licenses in a hat: | We're going to put the names of 6 open source licenses in a hat: |