Skip to main content

Initial Settings : Firewall

 [1]. It's possible to show FireWall Service Status like follows. (enabled by default)

[root@localhost ~]# systemctl status firewalld

*  firewalld.service - firewalld - dynamic firewall daemon

   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor p>

   Active: active (running) since Wed 2019-09-24 23:16:35 JST; 18min ago

     Docs: man:firewalld(1)

 Main PID: 801 (firewalld)

    Tasks: 2 (limit: 25025)

   Memory: 30.9M

   CGroup: /system.slice/firewalld.service

           └─801 /usr/libexec/platform-python -s /usr/sbin/firewalld --nofork ->


Sep 24 23:16:34 localhost.localdomain systemd[1]: Starting firewalld - dynamic >

Sep 24 23:16:35 localhost.localdomain systemd[1]: Started firewalld - dynamic f>


# [Active: active (running) ***] means firewalld is running now

[2].   If you use FireWall service, it needs to modify FireWall settings manually because incoming requests for services are mostly not allowed by default.

Refer to here for basic Firewall operation and settins.

Configuration examples of CentOS 8 on this site are based on the environment Firewalld service is always enabled.

[3]. If you don't need FireWall service because of some reasons like that some FireWall Machines are running in your Local Netowrk or others, it's possbile to stop and disable FireWall service on CentOS server like follows.

# stop service

[root@localhost ~]# systemctl stop firewalld

# disable service

[root@localhost ~]# systemctl disable firewalld

Removed /etc/systemd/system/multi-user.target.wants/firewalld.service.

Removed /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.

Initial Settings : SELinux

[4] It's possible to show current SELinux (Security-Enhanced Linux) Status like follows. (enabled by default)

[root@localhost ~]# getenforce

Enforcing     # SELinux is enabled

[5].  If you enable SELinux, there are cases to modify SELinux policy manually because sometimets SELinux stop applications.

Refer to here for basic SELinux operation and settins.

Configuration examples of CentOS 8 on this site are based on the environment SELinux is always Enforcing.

[6]. If you don't need SELinux feature because of some reasons like that your server is running only in Local safety Network or others, it's possbile to disable SELinux like follows.

[root@localhost ~]# vi /etc/selinux/config

# This file controls the state of SELinux on the system.

# SELINUX= can take one of these three values:

#     enforcing - SELinux security policy is enforced.

#     permissive - SELinux prints warnings instead of enforcing.

#     disabled - No SELinux policy is loaded.

# change the value below

# enforcing  ⇒ enabled

# disabled   ⇒ disabled

# permissive ⇒ enabled but only loging, not deny accesses

SELINUX=disabled

# SELINUXTYPE= can take one of these two values:

#     targeted - Targeted processes are protected,

#     minimum - Modification of targeted policy. Only selected processes are protected.

#     mls - Multi Level Security protection.

SELINUXTYPE=targeted


# restart computer to apply setting

[root@localhost ~]# reboot


Comments

Popular posts from this blog

Lambda Function with Amazon SNS

  Amazon SNS is a service used for push notification. In this chapter, we will explain working of AWS Lambda and Amazon SNS with the help of an example where will perform the following actions − Create Topic in SNS Service and use AWS Lambda Add Topics to CloudWatch Send SNS text message on phone number given. Requisites To create Topic in SNS Service and use AWS Lambda Add Topics to CloudWatch, we need not follow the steps given below − Create Topic in SNS Create Role for permission in IAM Create AWS Lambda Function Publish to topic to activate trigger Check the message details in CloudWatch service. To send SNS text message on phone number given, we need to do the following − Add code in AWS Lambda to send message to your phone. Example In this example, we will create a topic in SNS. When details are entered in the topic to publish, AWS Lambda is triggered. The topic details are logged in CloudWatch and a message is sent on phone by AWS Lambda. Here is a basic block diagram which exp

Unix / Linux - Shell Functions

W e will discuss in detail about the shell functions. Functions enable you to break down the overall functionality of a script into smaller, logical subsections, which can then be called upon to perform their individual tasks when needed. Using functions to perform repetitive tasks is an excellent way to create  code reuse . This is an important part of modern object-oriented programming principles. Shell functions are similar to subroutines, procedures, and functions in other programming languages. Creating Functions To declare a function, simply use the following syntax − function_name () { list of commands } The name of your function is  function_name , and that's what you will use to call it from elsewhere in your scripts. The function name must be followed by parentheses, followed by a list of commands enclosed within braces. Example Following example shows the use of function − #!/bin/sh # Define your function here Hello () { echo "Hello World" } # Invoke yo

Unix / Linux - Shell Input/Output Redirections

W e will discuss in detail about the Shell input/output redirections. Most Unix system commands take input from your terminal and send the resulting output back to your terminal. A command normally reads its input from the standard input, which happens to be your terminal by default. Similarly, a command normally writes its output to standard output, which is again your terminal by default. Output Redirection The output from a command normally intended for standard output can be easily diverted to a file instead. This capability is known as output redirection. If the notation > file is appended to any command that normally writes its output to standard output, the output of that command will be written to file instead of your terminal. Check the following  who  command which redirects the complete output of the command in the users file. $ who > users Notice that no output appears at the terminal. This is because the output has been redirected from the default standard output dev