LPIC-303 Objectives V1 - Revision history

FabianThorns: /* Introduction */

2019-05-03T09:57:40Z

Introduction

← Older revision		Revision as of 09:57, 3 May 2019
Line 1:		Line 1:
	__FORCETOC__		__FORCETOC__
	==Introduction==		==Introduction==
	The description of the entire [[LPIC-3]] ~~programme~~ is listed [[LPIC-3\|here]].		The description of the entire [[LPIC-3]] program is listed [[LPIC-3\|here]].
	<br />		<br />
	<br />		<br />

GMatthewRice: /* Version Information */

2015-02-11T12:07:22Z

Version Information

← Older revision		Revision as of 12:07, 11 February 2015
Line 6:		Line 6:

	==Version Information==		==Version Information==
	These objectives are version 1.0.0.
			These objectives are version 1.0.0.

			The version [[LPIC-303 Objectives V2\|2.x objectives]] can be found [[LPIC-303 Objectives V2\|here]].

	<br />		<br />

	==Translations of Objectives==		==Translations of Objectives==
	The following translations of the objectives are available on this wiki:		The following translations of the objectives are available on this wiki:

GMatthewRice: moved LPIC-303 to LPIC-303 Objectives V1

2015-02-11T12:02:14Z

moved LPIC-303 to LPIC-303 Objectives V1

← Older revision	Revision as of 12:02, 11 February 2015
(No difference)

Babafou: /* 320.2 Advanced GPG */ fix a few typos

2015-01-26T18:33:36Z

320.2 Advanced GPG: fix a few typos

← Older revision		Revision as of 18:33, 26 January 2015
Line 43:		Line 43:
	\|-		\|-
	\| style="background:#dadada; padding-right:1em" \| '''Description'''		\| style="background:#dadada; padding-right:1em" \| '''Description'''
	\| style="background:#eaeaea" \| Candidates should know how to use GPG. This includes key generation, signing and publishing to ~~keyservers~~. Managing multiple private ~~key~~ and IDs is also included.		\| style="background:#eaeaea" \| Candidates should know how to use GPG. This includes key generation, signing and publishing to key servers. Managing multiple private keys and IDs is also included.
	\|}		\|}
	'''Key Knowledge Areas:'''		'''Key Knowledge Areas:'''
	* GPG ~~encyption~~ and signing		* GPG encryption and signing
	* private/public key management		* private/public key management
	* GPG key servers		* GPG key servers
Line 56:		Line 56:
	* ~/.gnupg/		* ~/.gnupg/
	<br />		<br />

	====<span style="color:navy">320.3 Encrypted Filesystems</span>====		====<span style="color:navy">320.3 Encrypted Filesystems</span>====
	{\|		{\|

GMatthewRice: /* Other Comments for consideration */

2014-07-31T11:48:20Z

Other Comments for consideration

← Older revision		Revision as of 11:48, 31 July 2014
Line 569:		Line 569:

	This should be covered.		This should be covered.

			8) DNS

			More DNSSEC and DANE.

GMatthewRice: /* 390.4 System Security Services Daemon (weight: 2) */

2014-06-19T12:38:39Z

390.4 System Security Services Daemon (weight: 2)

← Older revision		Revision as of 12:38, 19 June 2014
Line 513:		Line 513:
	<br />		<br />
	<br />		<br />

			==Other Comments for consideration==

			Secure development, hardening

			As examples, following items are not in the current objectives:

			1) Related to Wireless LAN:

			(Note: It’s not only for Linux though, it is necessary to consider because

			there are many points to be taken care for configuration in terms of security

			measure.)

			2) Related to IPv6:

			Not only IPv4, but also IPv6 should be considered.

			3) Security features in Linux:

			For example, ASLR and Exec-Shield (ASCII Armor) should be considered,

			because it causes security level lower if those are disabled.

			4) Related to Forensics:

			In the survey of malware’s behavior, Sleuth Kit would be used to analyze

			the hard disk on Linux machine. Also in some cases, LVM commands would be

			used to restore the disk which became un-mountable.

			So that this area should be learned.

			5) Database (RDB, NoSQL) security:

			Because Application Security (bind, apache, etc.) is covered now, this item

			would be nice to cover. And this item is listed in the CIF, security contest

			almost every time.

			Also the counter-measure in server side is necessary.

			6) Related to OpenFlow:

			There are several points to be considered in terms of security measure about

			the configuration of OpenFlow.

			7) RADIUS

			This was covered in 301 though, this is not covered now.

			This should be covered.

Babafou: /* 322.4 FTP */ changed vsftp.conf to vsftpd.conf (missing d)

2013-11-25T17:13:27Z

322.4 FTP: changed vsftp.conf to vsftpd.conf (missing d)

← Older revision		Revision as of 17:13, 25 November 2013
Line 209:		Line 209:
	'''The following is a partial list of the used files, terms and utilities:'''		'''The following is a partial list of the used files, terms and utilities:'''
	* SSL/TLS		* SSL/TLS
	* ~~vsftp~~.conf		* vsftpd.conf
	<br />		<br />

	====<span style="color:navy">322.5 OpenSSH</span>====		====<span style="color:navy">322.5 OpenSSH</span>====
	{\|		{\|

GMatthewRice: /* Introduction */

2013-06-20T19:01:41Z

Introduction

← Older revision		Revision as of 19:01, 20 June 2013
Line 1:		Line 1:
	__FORCETOC__		__FORCETOC__
	==Introduction==		==Introduction==
	~~TODO: Need a~~ description ~~for exam~~ here		The description of the entire [[LPIC-3]] programme is listed [[LPIC-3\|here]].
	<br />		<br />
	<br />		<br />

	==Version Information==		==Version Information==
	These objectives are version 1.0.0.		These objectives are version 1.0.0.

GMatthewRice: /* 324.5 OpenVPN */

2013-06-04T14:09:09Z

324.5 OpenVPN

← Older revision		Revision as of 14:09, 4 June 2013
Line 370:		Line 370:
	* /etc/openvpn/		* /etc/openvpn/
	* openvpn server and client		* openvpn server and client



			==Future consideration not part of current exam==

			===''Topic 390: FreeIPA and Kerberos''===

			====<span style="color:navy">390.1 Deploying Kerberos (weight: 2)</span>====

			{\|
			\| style="background:#dadada" \|

			'''Weight'''

			\| style="background:#eaeaea" \| 2
			\|-
			\| style="background:#dadada; padding-right:1em" \|

			'''Description'''

			\| style="background:#eaeaea" \|

			Candidates should be familiar with deploying a Kerberos on a single domain.

			\|}

			'''Key Knowledge Areas:'''

			* Key Distribution Centre
			* Principals
			* Tickets

			'''The following is a partial list of the used files, terms and utilities:'''

			* kinit
			* krb5.conf
			* krb5kdc/kdc.conf
			* kdb5_util
			* rb5kdc/kadm5.acl
			* klist
			* kadmin, kadmin.local

			<br />

			====<span style="color:navy">390.2 FreeIPA Installation (weight: 2)</span>====

			{\|
			\| style="background:#dadada" \|

			'''Weight'''

			\| style="background:#eaeaea" \| 2
			\|-
			\| style="background:#dadada; padding-right:1em" \|

			'''Description'''

			\| style="background:#eaeaea" \|

			Candidates should be familiar with FreeIPA v3.x installation process of creating a server instance. Knowledge of the components used by FreeIPA.

			\|}

			'''Key Knowledge Areas:'''

			* System and configuration prerequisites for installing FreeIPA
			* FreeIPA Components: LDAP, Kerberos, PKI, DNS, Certmonger

			'''The following is a partial list of the used files, terms and utilities:'''

			* ipa-server-install and options
			* ipa

			<br />

			====<span style="color:navy">390.3 Integrating FreeIPA with Samba (weight: 2)</span>====

			{\|
			\| style="background:#dadada" \|

			'''Weight'''

			\| style="background:#eaeaea" \| 2
			\|-
			\| style="background:#dadada; padding-right:1em" \|

			'''Description'''

			\| style="background:#eaeaea" \|

			Candidates should be able to integrate with Samba for group management, Kerberized CIFS and as an AD DC with FreeIPA.

			\|}

			'''Key Knowledge Areas:'''

			* Cross-realm trusts

			'''The following is a partial list of the used files, terms and utilities:'''

			* ipa trust-add-ad
			* ipa config-mod
			* net
			* ldapadd

			<br />

			====<span style="color:navy">390.4 System Security Services Daemon (weight: 2)</span>====

			{\|
			\| style="background:#dadada" \|

			'''Weight'''

			\| style="background:#eaeaea" \| 2
			\|-
			\| style="background:#dadada; padding-right:1em" \|

			'''Description'''

			\| style="background:#eaeaea" \|

			Candidates should be able to configure and use SSSD manage access to remote directories and authentication mechanisms

			\|}

			'''Key Knowledge Areas:'''

			* SSSD daemon and command line tools
			* Configuring NSS and PAM for use with SSSD
			* Authenticate against a local, LDAP and Kerberos domain

			'''The following is a partial list of the used files, terms and utilities:'''

			* SSSD
			* sss_* commands
			* sssd.conf
			* nsswitch.conf

			<br />
			<br />

GMatthewRice: /* Version Information */

2011-06-24T20:36:47Z

Version Information

← Older revision		Revision as of 20:36, 24 June 2011
Line 7:		Line 7:
	These objectives are version 1.0.0.		These objectives are version 1.0.0.
	<br />		<br />
			==Translations of Objectives==
			The following translations of the objectives are available on this wiki:
			* [[LPIC-303\|English]]
			* [[LPIC-303(ES)\|Spanish]]
	<br />		<br />

	==Objectives==		==Objectives==
	===''Topic 320: Cryptography''===		===''Topic 320: Cryptography''===