Difference between revisions of "Meeting-20130209"

Jump to: navigation, search
(Schedule for the Day: Added an extra hour to the schedule to accommodate all the programming that's planned)
(Meeting Staff)
Line 71: Line 71:
* Snacks/Refreshments: Your name here
* Snacks/Refreshments: Your name here
* Setup: Your name here
* Setup: Your name here
* Clean Up: Your name here
* Clean Up: [[User:Vance|Vance Kochenderfer]], Your name here
== Carpooling ==
== Carpooling ==

Revision as of 22:39, 3 February 2013

WPLUG will hold a general user meeting on Saturday, February 9, 2013 at the Wilkins School Community Center in Swissvale, PA. You don't need to be a member of WPLUG to come to our meetings, and there is no cost to attend.

After our "business meeting," which typically doesn't take more than half an hour, we'll open the floor to presentations, discussions, and generally just hanging out. If you're interested in having fun with other Linux and open source enthusiasts in the area, we invite you to stop by!

Schedule for the Day

1:30pm - Doors open, set up

2:00pm - Business Meeting starts

2:30pm - Presentations (topics listed below)

4:30pm - Meeting ends, everyone out. Some of us may go to D's 6pack for beer and dogs.

Business Meeting

  • Review of minutes (5 minutes)
  • Reports of officers (10 minutes)
  • Cast/count ballots for bylaws amendment advanced at January GUM (10 minutes)
  • Commission to Reform WPLUG presents Reform Package 2, a collection of changes designed to take WPLUG on an exciting new direction
  • New business


Presentation: Build Your Own Certificate Authority Using xca

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?

The no-cost alternative is to create your own private CA, and register it as a trusted certificate issuer on your systems. Linux distributions already include all the tools you need to do this, in the OpenSSL package - but the procedures for creating a CA and issuing certificates using the raw OpenSSL tools are obscure, complicated, and can only be done from the command line.

In this presentation, I will give a (very) brief overview of Public Key Infrastructure (a/k/a "PKI" - the general framework that supports certificate-based security), and talk just a little about how it works and what it's used for. You will learn about "xca" (packaged for many mainstream Linux distros, and also available for Windows and Mac OS), an open source GUI interface to OpenSSL that makes managing a private CA quick and simple. You will learn how to use "xca" to create a private root CA and generate your first server certificate - a process that, using the "xca" GUI, can be completed in two minutes or less. You will learn how to register your private root CA as a trusted certificate issuer in Firefox and Internet Explorer (yeah, I know ... but people do use it...). Finally, I will briefly describe how to use the server certificate you generated from your private root CA to secure your Apache-based web server.

If there is interest, possible future presentations may cover topics such as how to use your private CA to issue client certificates that can be used for client-based web authentication, and to secure private VPNs (such as you might build using OpenVPN, for remote connectivity into your home network, etc.).

Presentation: The Rise and Fall of the WebOS Mobile Operating System

"In the span of just three years, webOS went from being a media darling to a running gag. What happened? How did it end up contributing to Android's development? I'll also be giving a hands-on demonstration of Open WebOS, the most current iteration of webOS, since I own one of the three Android devices that is capable of running it."

"Hot Seat" Discussion Event: Open Source License Smackdown!

  • Participants: Pat Barron, Justin Smith, Terry Golightly, Joe Prostko, plus anyone else who wants to try

We're going to put the names of 6 open source licenses in a hat:

  • LGPL v3
  • GPL v3
  • Apache License
  • MIT License
  • Mozilla Public License
  • Microsoft Reciprocal License

Everyone who wants to participate will take a license from the hat and defend why it's the "best" for 5 minutes or so. The event will be a series of rapid-fire discussions like you might see on ESPN.

At the very least, four members of our Board of Directors - Chair Pat, yours truly, Treasurer Terry, and Director-at-Large Joe - will participate. If other people want to try, we'll add more licenses to the hat as necessary to accommodate them. If you get a license you don't know about, we'll give you basic information about it and a few minutes to think over what to say.

If you don't want to sit in the hot seat, that's fine! Just sit back, relax, and learn about all the different ways you can "do" open source. Will someone who hates one of these licenses have to defend it? (I hope I don't get Apache or MIT...) Which poor sap will get the Microsoft license? Tune in and find out!

Meeting Minutes

To be posted after the meeting is over.

Meeting Staff

If you'd like to assist with this meeting, please add your name to one or more of the categories below.

  • Host: Your name here
  • Co-Host: Your name here
  • Snacks/Refreshments: Your name here
  • Setup: Your name here
  • Clean Up: Vance Kochenderfer, Your name here


  • Your name/location here