Meeting-20130209 - Revision history

Centinel: /* Speaker/Presentation */ Added a link to my software license summary.

2013-02-14T04:20:01Z

Speaker/Presentation: Added a link to my software license summary.

← Older revision		Revision as of 04:20, 14 February 2013
Line 56:		Line 56:
	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.		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.		At the very least, four members of our Board of Directors - Chair Pat, Vice Chair/Secretary Justin, 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!		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!

			If you'd like to learn more about software licenses, Justin put together a handout that gives a plain English, one-page summary for each of the six in our debate panel (MIT, Apache, Mozilla Public, Microsoft Reciprocal, LGPL, GPL). It also includes an "inheritance chart" that shows how the licenses get progressively more complex. If you'd like a copy, here's the link:

			http://www.js-wordsmith.com/wp-content/uploads/2013/02/software-license-notes-final.odt

	== Meeting Minutes ==		== Meeting Minutes ==

Centinel: /* Meeting Minutes */ Added this month's minutes.

2013-02-14T03:49:20Z

Meeting Minutes: Added this month's minutes.

@@ Line 62: / Line 62: @@
 == Meeting Minutes ==
-To be posted after the meeting is over.
+'''MEETING START'''
 == Meeting Staff ==

Vance: /* Meeting Staff */

2013-02-03T22:39:00Z

Meeting Staff

← Older revision		Revision as of 22:39, 3 February 2013
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 ==

Patbarron: /* Schedule for the Day */ Added an extra hour to the schedule to accommodate all the programming that's planned

2013-02-03T06:17:46Z

Schedule for the Day: Added an extra hour to the schedule to accommodate all the programming that's planned

← Older revision		Revision as of 06:17, 3 February 2013
Line 11:		Line 11:
	2:30pm - Presentations (topics listed below)		2:30pm - Presentations (topics listed below)

	3:30pm - Meeting ends, everyone out. Some of us may go to [http://www.ds6pax.com/ D's 6pack] for beer and dogs.		4:30pm - Meeting ends, everyone out. Some of us may go to [http://www.ds6pax.com/ D's 6pack] for beer and dogs.

	== Business Meeting ==		== Business Meeting ==

Centinel: /* Speaker/Presentation */

2013-02-02T23:54:12Z

Speaker/Presentation

← Older revision		Revision as of 23:54, 2 February 2013
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]]		*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]]		*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!'''
			*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:		We're going to put the names of 6 open source licenses in a hat:

Centinel: /* Speaker/Presentation */

2013-02-02T23:52:39Z

Speaker/Presentation

@@ Line 23: / Line 23: @@
 == Speaker/Presentation ==
 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?
@@ Line 35: / Line 34: @@
 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.).
 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
 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."
 == Meeting Minutes ==

Centinel: /* Business Meeting */

2013-02-02T23:50:16Z

Business Meeting

← Older revision		Revision as of 23:50, 2 February 2013
Line 18:		Line 18:
	* Reports of officers (10 minutes)		* Reports of officers (10 minutes)
	* Cast/count ballots for bylaws amendment advanced at January GUM (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		* New business

Patbarron: /* Schedule for the Day */ Add post-meeting venue link (D's has their own web site now)

2013-02-01T21:25:47Z

Schedule for the Day: Add post-meeting venue link (D's has their own web site now)

← Older revision		Revision as of 21:25, 1 February 2013
Line 11:		Line 11:
	2:30pm - Presentations (topics listed below)		2:30pm - Presentations (topics listed below)

	3:30pm - Meeting ends, everyone out. Some of us may go to D's 6pack for beer and dogs.		3:30pm - Meeting ends, everyone out. Some of us may go to [http://www.ds6pax.com/ D's 6pack] for beer and dogs.

	== Business Meeting ==		== Business Meeting ==

Patbarron: /* Speaker/Presentation */

2013-02-01T17:10:18Z

Speaker/Presentation

← Older revision		Revision as of 17:10, 1 February 2013
Line 26:		Line 26:
	Topic: Build Your Own Certificate Authority Using xca		Topic: Build Your Own Certificate Authority Using xca

	''(~~Abstract~~ to ~~follow~~)''		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.).

	Presenter: [[User:Centinel\|Justin Smith]]		Presenter: [[User:Centinel\|Justin Smith]]

Patbarron: /* Speaker/Presentation */ With both of the scheduled presentations, the day's schedule is now basically full

2013-02-01T16:31:49Z

Speaker/Presentation: With both of the scheduled presentations, the day's schedule is now basically full

← Older revision		Revision as of 16:31, 1 February 2013
Line 34:		Line 34:
	"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
	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."		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."

	There is still room on the schedule for one additional 20 to 30 minute presentation. If you're interested in making a presentation, please contact the Program Committee: [mailto:events@wplug.org events@wplug.org].

	== Meeting Minutes ==		== Meeting Minutes ==