LILUG - Recent changes [en]

Lilug

2012-05-16T04:17:34Z

Added section for prior meeting minutes

← Older revision		Revision as of 04:17, 16 May 2012
(One intermediate revision by one user not shown)
Line 6:		Line 6:
	*The next Lilug meeting is: <nextmeetingdesc type="link" group="lilug"><meetingdatetime group="lilug"></meetingdatetime></nextmeetingdesc>		*The next Lilug meeting is: <nextmeetingdesc type="link" group="lilug"><meetingdatetime group="lilug"></meetingdatetime></nextmeetingdesc>
	*The next Lilug [[Lilug_IRC \|IRC meeting]] is: <meetingdatetime group="lilugirc"></meetingdatetime>		*The next Lilug [[Lilug_IRC \|IRC meeting]] is: <meetingdatetime group="lilugirc"></meetingdatetime>
		+
		+	== Previous General Meeting Minutes ==
		+	The [[LILUG_General_Meeting_-_Tuesday,_8_May,_2012 \| May meeting minutes]] are now available.
		+
		+	Minutes for past meetings may be found by going to the [[Meetings]] link in the main menu and then looking at the archives section.

	== Special Interest Group ==		== Special Interest Group ==

LILUG General Meeting - Tuesday, 8 May, 2012

2012-05-14T00:54:06Z

Created page with "__NOTOC__ ==Meeting Summary== LILUG President Matt Newhall opened the meeting at 20:03. ===Speaker=== '''Matt Surico - GNU Privacy Guard and Cryptography, Part One''' LILUG S..."

New page

__NOTOC__
==Meeting Summary==

LILUG President Matt Newhall opened the meeting at 20:03.

===Speaker===

'''Matt Surico - GNU Privacy Guard and Cryptography, Part One'''

LILUG Secretary Matt Surico gave the first in his planned two-part talk series on [http://gnupg.org GNU Privacy Guard (GPG)].

Matt began his talk by explaining the etymology of the word "cryptography" and went on to define the word (which basically means "hidden writing", and covers both the "hiding/unhiding" of messages, as well as the creating and verification of digital signatures).

Matt showed an example of steganography (as an aside); he then defined important terms in cryptography like encryption, decryption, cipher, ciphertext, plaintext and key. He also showed that "codes" and "ciphers" are two slightly different things.

He gave several examples of how cryptography has been used throughout history.

In the next section of his talk, Matt pointed out that Pretty Good Privacy (PGP), OpenPGP and GPG were all directly related. He detailed the history behind PGP and how the OpenPGP standard came to be. This was followed by an explanation of symmetric vs. asymmetric ciphers. Matt pointed out that OpenPGP is a hybrid crypto system, comprised of compression, hashing, asymmetric (public key) and symmetric elements.

Matt explained how asymmetric keys are created and how they are used. He also showed how OpenPGP works. Finally, Matt introduced GPG and gave a live demonstration of how it can be used.

At the conclusion, Matt detailed the steps by which LILUG members can prepare for June's key signing party.

Matt's [[media:M Surico Presentation GPG Part One 8 May 2012.pdf | slideset in PDF format]] is available for download.

===Group Discussion===

====Red Hat Enterprise Linux====

Matt N. began this topic by mentioning that Red Hat was upping the price on the licensing (which includes support) for the latest version of Red Hat Enterprise Linux (RHEL). This evolved into a discussion about what RHEL is and what clones of the distribution (such as CentOS and Oracle Linux) are available.

===Announcement===

The Long Island chapter of the [https://www.owasp.org/index.php/Main_Page Open Web Application Security Project] will be having a meeting on Thursday 10 May at Adelphi University on the subject of Mobile Security. It will be from 7:30 to 9:00 PM in the IT conference room in the lower level of Hagedorn Hall of Enterprise.

Matt N. closed the meeting at 22:03.

[[User:Msurico|Msurico]] 17:54, 13 May 2012 (PDT)

==Contributed Notes on Meeting From Others==

- none

Meetings 2012

2012-05-14T00:24:17Z

Added link to May meeting minutes

← Older revision		Revision as of 00:24, 14 May 2012
Line 1:		Line 1:
	== LILUG General Meetings: 2012 ==		== LILUG General Meetings: 2012 ==

		+	[[LILUG General Meeting - Tuesday, 8 May, 2012\|8 May, 2012]]

	[[LILUG General Meeting - Tuesday, 10 April, 2012\|10 April, 2012]]		[[LILUG General Meeting - Tuesday, 10 April, 2012\|10 April, 2012]]

File:M Surico Presentation GPG Part One 8 May 2012.pdf

2012-05-14T00:02:59Z

uploaded "[[File:M Surico Presentation GPG Part One 8 May 2012.pdf]]" This is the slideset from the first in a two-part presentation series on GNU Privacy Guard that Matt Surico gave to LILUG.

Template:Lilug Meeting 2012 07

2012-05-11T11:30:29Z

Created page with "__NOTOC__ ====Meeting Place & Time==== <meetingdatetime group="lilug" month="07" year="2012"></meetingdatetime> at the Woodbury Campus of Cold Spring Harbor Lab, in the Woodbury..."

New page

__NOTOC__
====Meeting Place & Time====

<meetingdatetime group="lilug" month="07" year="2012"></meetingdatetime> at the Woodbury Campus of Cold Spring Harbor Lab, in the Woodbury Auditorium

====Topic====
Meeting topic TBD.

Meetings

2012-05-11T11:29:04Z

Removed May mtg link, added July mtg link

← Older revision		Revision as of 11:29, 11 May 2012
Line 8:		Line 8:
	----		----
	'''Upcoming General Monthly Meetings'''		'''Upcoming General Monthly Meetings'''
−
−	~~[[Template:Lilug_Meeting_2012_05\|May 2012]]~~

	[[Template:Lilug_Meeting_2012_06\|June 2012]]		[[Template:Lilug_Meeting_2012_06\|June 2012]]
		+
		+	[[Template:Lilug_Meeting_2012_07\|July 2012]]

	----		----

Template:Lilug Meeting 2012 06

2012-05-10T18:04:26Z

Linked to the key signing instructions

← Older revision		Revision as of 18:04, 10 May 2012
Line 11:		Line 11:
	In this second installment, Matt will review the concepts of cryptography and the use of GPG introduced at the May meeting. He'll demonstrate the use of OpenPGP in an email client, and then discuss key management. The applicability of cryptographic principles to SSH and SSL will be shown, and a discussion of trust and digital certificates will also be had.		In this second installment, Matt will review the concepts of cryptography and the use of GPG introduced at the May meeting. He'll demonstrate the use of OpenPGP in an email client, and then discuss key management. The applicability of cryptographic principles to SSH and SSL will be shown, and a discussion of trust and digital certificates will also be had.

−	Finally, a key signing will take place. ~~Instructions~~ for the key signing ~~will be~~ posted ~~here very soon as well as~~ on the mailing list.	+	Finally, a key signing will take place. Be sure to check out the [[May 2012 GPG Key Generation and Collection \| instructions for the key signing]]. These are also being posted on the LILUG general mailing list.

	'''Don't worry - If you missed the May meeting you can still take place in the key signing!'''		'''Don't worry - If you missed the May meeting you can still take place in the key signing!'''

May 2012 GPG Key Generation and Collection

2012-05-10T02:54:02Z

New page

__NOTOC__

To properly prepare for the June 2012 GPG key signing, please follow the directions below. It's ok if you didn't make it to the May presentation - you can still participate in the June key signing!

===Install GPG===

These instructions are meant for those who have GnuPG installed. If you don't already have it, get it from your distro's package repository or from the [http://www.gnupg.org GnuPG website].

'''Note:''' If you have a different OpenPGP-compliant tool that you'd like to use, that's ok. Contact Matt Surico [mailto:secretary_AT_lilug_DOT_org (me)] with details and I'll help you out. I'll also consider posting the instructions to the group in case others are using the same tool. No matter how you generate your keys, everyone will need to send his/her public key to LILUG for collation.

===Generate the keypair===

If you don't already have a keypair, use this command from your shell prompt:

$ gpg --gen-key

You want to make the DSA and Elgamal key type - this will allow you to
encrypt as well as sign files with your key-pair. The key-size should be
anything between 2048 and 4096. The larger the key, the harder it is
to "crack". However the time required to sign and encrypt documents with it
increases as well. Then follow the remaining on screen instructions. When the key is generated, information about it will be printed. Here is an example:

pub 2048D/20E323B4 2012-05-10
uid John Doe <someguy@example.com>
sub 2048g/E261003E 2012-05-10

The first hexadecimal number identifies your key. In this case, ''20E323B4''
is John Doe's key.

===Generate a revocation certificate===

This is always a good idea to do right away, just in case your private key ever gets compromised. From your shell prompt:

$ gpg --gen-revoke

===Export the public key===

You will be exporting as an ''ASCII-armored'' file. Use this command from your shell prompt:

$ gpg -a --export hex_key_id > hex_key_id.asc

In the example key above, John Doe would do:

$ gpg -a --export 20E323B4 > 20E323B4.asc

===Send the public key to our LILUG collection address===

I have set up a special email account for LILUG to collect public keys. Just email that hex_key_id.asc file to [mailto:keysigning_AT_lilug_DOT_org us]. I will assemble them and create the list with all the keys.

'''The deadline to submit your public key to be a part of the June key signing is Friday 25 May 2012 11:59 PM EDT.'''

===Check your key listing on the wiki===

I will be posting the list of all keys received on this wiki by Monday 28 May (and will send out a note to the LILUG mailing list). It is very important you verify that I didn't make an error in representing your key. Send an email to the keysigning address if you see something wrong by Friday 1 June 2012 11:59 PM EDT. No need to email if everything is ok.

===Things you need to prepare prior to the June meeting===

Once the list of all keys has been posted to the wiki, and before you come to the June meeting you must:

# Print out the entire list of keys. This is your personal sheet where you'll be able to mark whether you trust each key and the keyholder at the keysigning. Bring that to the June meeting.
# Print out your fingerprint by using this command and sending the entire output to a printer, and bring that to the meeting also:

$ gpg --fingerprint hex_key_id

Please bring a form of ID to the June meeting that includes a photograph (such as a passport, school ID card, or driver's license). That will be part of the verification process we'll go through.

===Questions? Problems?===

If you have any questions, feel free to ask them on the LILUG mailing list or
email me privately.

Thanks, and keep watching the mailing list for any updates.

''Matt Surico, LILUG Secretary''