Free LPI 202-450 Practice Exam with Questions & Answers | Set: 3

The PAM module that sets and unsets environment variables is pam_env. This module allows the (un)setting of environment variables based on the rules specified in the configuration file /etc/security/pam_env.conf or an alternative file. The module can also read a file with simple KEY=VAL pairs on separate lines (/etc/environment by default) or a user-specific file ($HOME/.pam_environment by default). The pam_env module supports the use of previously set environment variables as well as PAM_ITEMs such as PAM_RHOST. The pam_env module should be the last one on the stack, as setting PAM environment variables can have side effects on other modules. The pam_env module provides the auth and session module types. References:

• pam_env - PAM module to set/unset environment variables
• pam_env(8) - Linux manual page

Sieve filters are usually applied to an email when the email is delivered to a mailbox by a mail delivery agent (MDA) or a local delivery agent (LDA). Sieve filters are scripts that can perform various actions on incoming emails, such as sorting them into folders, assigning labels, forwarding, rejecting, or discarding them. Sieve filters are executed on the server side, and they are independent of the mail user agent (MUA) or the mail access protocol. This means that the email filtering is consistent across different email clients and devices. Sieve filters are not applied when the email is relayed by an SMTP server, received by an SMTP smarthost, sent to the first server by an MUA, or retrieved by an MUA. These are different stages of the email delivery process, but they do not involve the final delivery of the email to a mailbox.

References:

• LPIC-2 Exam 202 Objectives, Objective 205.4: Managing a dovecot server
• Sieve filter (advanced custom filters) | Proton
• start - Sieve.Info
• What is Sieve Filtering? - Knowledge Base - Pair Networks

The option in the sshd configuration file that instructs sshd to permit only specific user names to log in to a system is AllowUsers. This option can be followed by a list of user name patterns, separated by spaces, that are allowed to log in. For example:

AllowUsers alice bob

This will allow only alice and bob to log in via ssh. Any other user will be denied access. The AllowUsers option can also take the form USER@HOST to restrict logins to particular users from particular hosts. For example:

AllowUsers alice@192.168.1.* bob@example.com

This will allow alice to log in from any host in the 192.168.1.0/24 network, and bob to log in from the host example.com. The AllowUsers option can be used in conjunction with the DenyUsers option, which does the opposite. The allow/deny directives are processed in the following order: DenyUsers, AllowUsers, DenyGroups, and finally AllowGroups.

References:

• sshd_config - OpenSSH SSH daemon configuration file
• Allow Or Deny SSH Access To A Particular User Or Group In Linux - OSTechNix

 The objectClass attribute of an LDAP object defines which other attributes can be set for the object. The objectClass attribute is a multi-valued attribute that specifies one or more object classes that the object belongs to. Each object class has a schema that defines the mandatory and optional attributes that the object can have. The objectClass attribute is required for every LDAP object and determines the nature and characteristics of the object. References:

• Understanding the LDAP Protocol, Data Hierarchy, and Entry Components
• LDAP Object Classes

The LDIF file format does not accept any type of file encoding. It requires the file to be encoded in UTF-8, which is a Unicode encoding that supports all characters and languages. If the file contains non-UTF-8 characters, it may cause errors or data loss when importing or exporting LDIF data. Therefore, it is important to ensure that the LDIF file is encoded in UTF-8 before using it with LDAP tools or servers. References:

• LDIF File (What It Is and How to Open One) - Lifewire
• RFC 2849 - The LDAP Data Interchange Format (LDIF) - Technical Specification

 The options rw and ro are valid in /etc/exports. They specify whether the exported file system is mounted with read-write or read-only permissions by the clients. The option rw allows the clients to modify the files on the server, while the option ro prevents any changes by the clients. These options can be applied to all or specific hosts in the /etc/exports file123 References:

• LPIC-2 Overview
• LPIC-2 202-450
• 10 practical examples to export NFS shares in Linux | GoLinuxCloud

DANE stands for DNS-based Authentication of Named Entities. It is a protocol that provides a way to verify the association of X 509 certificates to DNS host names. X 509 certificates are digital documents that contain the public key and identity information of an entity, such as a web server or an email server. They are used to establish secure connections and authenticate the identity of the entity. However, the traditional way of obtaining and validating X 509 certificates relies on a hierarchical system of trusted third parties, called certificate authorities (CAs), which can be vulnerable to attacks or compromise. DANE aims to enhance the security and trust of X 509 certificates by using DNSSEC, which is a set of extensions to DNS that provide cryptographic signatures and validation for DNS records. DANE allows the owner of a domain name to publish the X 509 certificate or its fingerprint in a DNS record, called a TLSA record, which can be verified by the DNSSEC chain of trust. This way, the client can check the authenticity of the certificate directly from the DNS, without relying on external CAs. DANE can also be used to specify which CAs are authorized to issue certificates for a domain name, or to indicate that no CA is needed at all. DANE can be applied to various protocols that use X 509 certificates, such as HTTPS, SMTP, IMAP, POP3, etc.

References:

• DANE - Wikipedia
• DNS-Based Authentication of Named Entities (DANE) - Internet Society
• DANE: Taking TLS Authentication to the Next Level Using DNSSEC

The dig command in the image shows that the reverse DNS lookup for the IP address 192.168.0.1 failed to return the expected hostname linuserv.example.net. Instead, it returned linuserv.example.net.example.net, which indicates that the PTR record in the reverse lookup zone file is missing a dot (.) at the end of the hostname. Without the dot, the hostname is treated as relative to the zone name, which is example.net. Therefore, the correct syntax for the PTR record in the reverse lookup zone file should be:

1.168.192.in-addr.arpa. IN PTR linuserv.example.net.

The dot at the end of the hostname makes it absolute, meaning it does not append the zone name to it. This way, the reverse DNS lookup will return the correct hostname for the IP address123 References:

• Reverse DNS Lookup - WhatIsMyIP.com®
• DNS PTR Records - DNSimple Help
• How to Configure Reverse DNS for BIND in WHM - cPanel Knowledge Base - cPanel Documentation

What is a DNS PTR Record? PTR Record Syntax & Examples - PowerDMARC

The client-to-client option in OpenVPN enables the VPN server to forward packets between VPN clients internally, without sending them to the IP layer of the host system. This means that the host networking stack does not see or process the client-to-client traffic at all. This option can improve the performance and efficiency of the VPN, as well as reduce the load on the host system. However, it also means that the VPN server cannot apply any firewall rules or routing policies to the client-to-client traffic, as it would if the traffic passed through the host IP layer. Therefore, this option should be used with caution and only when the VPN clients are trusted and isolated from other networks. References:

• OpenVPN 2.x HOWTO, section “Client-to-client”
• OpenVPN 2.4 man page, option “–client-to-client”

To prevent anonymous FTP users from listing uploaded file names, the upload directory must not have the read or execute permission set for the anonymous user or group. The read permission allows the user to view the contents of a file or directory, while the execute permission allows the user to enter or search a directory. Therefore, removing both permissions will prevent the user from accessing or listing the files in the upload directory. However, the write permission can be left on, as it allows the user to create or modify files in the directory, which is the purpose of an upload directory. References:

• LPIC-2 Exam 202-450 Objectives, Topic 211: File Sharing, Objective 211.2: Manage FTP Service, Weight: 3
• LPIC-2 Linux Professional Institute Certification Study Guide: Exam 201 and Exam 202, Chapter 9: File Sharing, FTP, p. 353-354
• Linux File Permissions Explained, Read, Write, and Execute Permissions, p. 2-4