Différences

Ci-dessous, les différences entre deux révisions de la page.

--- articles:debian-setup-ufw [2024/11/29 14:56] – créée frater
+++ articles:debian-setup-ufw [2024/12/11 12:44] (Version actuelle) – frater
@@ Ligne 1: / Ligne 1: @@
-====== debian-setup-ufw ======
+====== UFW (Uncomplicated Firewall) ======
 ''UFW'', or //Uncomplicated Firewall//, is an interface to iptables that is geared towards simplifying the process of configuring a firewall.
@@ Ligne 7: / Ligne 7: @@
 If you’re looking to get started securing your network, and you’re not sure which tool to use, UFW may be the right choice for you.
+===== Requierements =====
 To follow this article, you will need:
   * A server running debian based distribution, along with a non-root user with ''sudo'' privileges.
-  * UFW is installed by default on debian. If it has been uninstalled for some reason, you can install it with ''sudo apt install ufw''.
+  * UFW is **NOT** installed by default on Debian. You can install it with ''sudo apt install ufw''.
 ===== Making Sure IPv6 is Enabled =====
@@ Ligne 41: / Ligne 42: @@
 To make sure you’ll be able to follow along with the rest of this tutorial, you’ll now set up your UFW default policies for incoming and outgoing traffic.
-To set the default UFW incoming policy to ''deny'', run:
+To ensure that the default UFW incoming policy is set to ''deny'', run:
 <cli bash>
 frater@vulkan:$ sudo ufw default deny incoming
+Default incoming policy changed to 'deny'
+(be sure to update your rules accordingly)
 </cli>
+To ensure that the default UFW  outgoing policy is set to ''allow'', run:
-Output
+<cli bash>
-Default incoming policy changed to 'deny'
+frater@vulkan:$ sudo ufw default allow outgoing
+Default outgoing policy changed to 'allow'
 (be sure to update your rules accordingly)
+</cli>
-To set the default UFW outgoing policy to allow, run:
+These commands set the defaults to ''deny'' incoming and ''allow'' outgoing connections. These firewall defaults alone might suffice for a personal computer, but servers typically need to respond to incoming requests from outside users. We’ll look into that next.
-    sudo ufw default allow outgoing
+===== Allowing SSH Connections =====
-Output
+If you were to enable your UFW firewall now, it would deny all incoming connections.
-Default outgoing policy changed to 'allow'
-(be sure to update your rules accordingly)
-These commands set the defaults to deny incoming and allow outgoing connections. These firewall defaults alone might suffice for a personal computer, but servers typically need to respond to incoming requests from outside users. We’ll look into that next.
+This means that you’ll need to create rules that explicitly allow legitimate incoming connections — SSH or HTTP connections, for example — if you want your server to respond to those types of requests. If you’re using a cloud server, you will probably want to allow incoming SSH connections so you can connect to and manage your server.
-Step 3 — Allowing SSH Connections
-If you were to enable your UFW firewall now, it would deny all incoming connections. This means that you’ll need to create rules that explicitly allow legitimate incoming connections — SSH or HTTP connections, for example — if you want your server to respond to those types of requests. If you’re using a cloud server, you will probably want to allow incoming SSH connections so you can connect to and manage your server.
+==== Allowing the OpenSSH UFW Application Profile ====
-Allowing the OpenSSH UFW Application Profile
 Upon installation, most applications that rely on network connections will register an application profile within UFW, which enables users to quickly allow or deny external access to a service. You can check which profiles are currently registered in UFW with:
-    sudo ufw app list
+<cli bash>
+frater@vulkan:$ sudo ufw app list
-Output
 Available applications:
+  AIM
+  Bonjour
+  CIFS
+  DNS
+  Deluge
+  IMAP
+  IMAPS
+  IPP
+  :
   OpenSSH
+  POP3
+  POP3S
+  PeopleNearby
+  SMTP
+  SSH
+  :
+  VNC
+  WWW
+  WWW Cache
+  WWW Full
+  WWW Secure
+  XMPP
+  :
+</cli>
 To enable the OpenSSH application profile, run:
-    sudo ufw allow OpenSSH
+<cli bash>
+frater@vulkan:$ sudo ufw allow OpenSSH
-Output
 Rule added
 Rule added (v6)
+</cli>
 This will create firewall rules to allow all connections on port 22, which is the port that the SSH daemon listens on by default.
-Allowing SSH by Service Name
-Another way to configure UFW to allow incoming SSH connections is by referencing its service name: ssh.
+==== Allowing SSH by Service Name ====
-    sudo ufw allow ssh
+Another way to configure UFW to allow incoming SSH connections is by referencing its service name: ''ssh''.
-Output
+<cli bash>
+frater@vulkan:$ sudo ufw allow ssh
 Rule added
 Rule added (v6)
+</cli>
+UFW knows which ports and protocols a service uses based on the ''/etc/services'' file.
-UFW knows which ports and protocols a service uses based on the /etc/services file.
+==== Allowing SSH by Port Number ====
-Allowing SSH by Port Number
 Alternatively, you can write the equivalent rule by specifying the port instead of the application profile or service name. For example, this command works the same as the previous examples:
-    sudo ufw allow 22
-Output
+<cli bash>
+frater@vulkan:$ sudo ufw allow 22
 Rule added
 Rule added (v6)
+</cli>
-If you configured your SSH daemon to use a different port, you will have to specify the appropriate port. For example, if your SSH server is listening on port 2222, you can use this command to allow connections on that port:
-    sudo ufw allow 2222
+<WRAP center round important>
+If you have configured your SSH daemon to use a different port, you will have to specify the appropriate port.
-Output
+For example, if your SSH server is listening on port 2222, you can use this command to allow connections on that port:
+<cli bash>
+frater@vulkan:$ sudo ufw allow 2222
 Rule added
 Rule added (v6)
+</cli>
+</WRAP>
+==== Commenting rules ====
+It's always a good idea to comment your rules for futur review; especially if you're using non standard tcp port or custom applications:
+<cli bash>
+frater@vulkan:$ sudo ufw allow 2222 comment 'This port allow SSH connection'
+Rule added
+Rule added (v6)
+</cli>
+You can add/modify comment to existing rules:
+<cli bash>
+frater@vulkan:$ sudo ufw allow 2222 comment 'This port allow MyPowerSSH connection'
+Rule updated
+Rule updated (v6)
+</cli>
+You can add also remove comment to existing rules:
+<cli bash>
+frater@vulkan:$ sudo ufw allow 2222 comment ''
+Rule updated
+Rule updated (v6)
+</cli>
 Now that your firewall is configured to allow incoming SSH connections, you can enable it.
-Step 4 — Enabling UFW
+===== Enabling UFW =====
 Your firewall should now be configured to allow SSH connections. To verify which rules were added so far, even when the firewall is still disabled, you can use:
-    sudo ufw show added
+<cli bash>
+frater@vulkan:$ sudo ufw show added
-Output
 Added user rules (see 'ufw status' for running firewall):
 ufw allow OpenSSH
+</cli>
 After confirming your have a rule to allow incoming SSH connections, you can enable the firewall with:
-    sudo ufw enable
+<cli bash>
+frater@vulkan:$ sudo ufw enable
-Output
 Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
 Firewall is active and enabled on system startup
+</cli>
-You will receive a warning that says the command may disrupt existing SSH connections. You already set up a firewall rule that allows SSH connections, so it should be fine to continue. Respond to the prompt with y and hit ENTER.
+You will receive a warning that says the command may disrupt existing SSH connections. You already set up a firewall rule that allows SSH connections, so it should be fine to continue. Respond to the prompt with ''y'' and hit ''ENTER''.
-The firewall is now active. Run the sudo ufw status verbose command to see the rules that are set. The rest of this tutorial covers how to use UFW in more detail, like allowing or denying different kinds of connections.
+The firewall is now active.
-Step 5 — Allowing Other Connections
-At this point, you should allow all of the other connections that your server needs to respond to. The connections that you should allow depend on your specific needs. You already know how to write rules that allow connections based on an application profile, a service name, or a port; you already did this for SSH on port 22. You can also do this for:
+Run the ''sudo ufw status verbose'' command to see the rules that are set. The rest of this tutorial covers how to use UFW in more detail, like allowing or denying different kinds of connections.
-    HTTP on port 80, which is what unencrypted web servers use, using sudo ufw allow http or sudo ufw allow 80
+===== Allowing Other Connections =====
-    HTTPS on port 443, which is what encrypted web servers use, using sudo ufw allow https or sudo ufw allow 443
-    Apache with both HTTP and HTTPS, using sudo ufw allow ‘Apache Full’
-    Nginx with both HTTP and HTTPS, using sudo ufw allow ‘Nginx Full’
-Don’t forget to check which application profiles are available for your server with sudo ufw app list.
+At this point, you should allow all of the other connections that your server needs to respond to. The connections that you should allow depend on your specific needs. You already know how to write rules that allow connections based on an application profile, a service name, or a port; you already did this for SSH on port ''22''. You can also do this for:
+  * HTTP on port 80, which is what unencrypted web servers use, using ''sudo ufw allow http'' or ''sudo ufw allow 80''
+  * HTTPS on port 443, which is what encrypted web servers use, using ''sudo ufw allow https'' or ''sudo ufw allow 443''
+  * Apache with both HTTP and HTTPS, using ''sudo ufw allow ‘Apache Full’''
+  * Nginx with both HTTP and HTTPS, using ''sudo ufw allow ‘Nginx Full’''
+Don’t forget to check which application profiles are available for your server with ''sudo ufw app list''.
 There are several other ways to allow connections, aside from specifying a port or known service name. We’ll see some of these next.
-Specific Port Ranges
+==== Specific Port Ranges ====
 You can specify port ranges with UFW. Some applications use multiple ports, instead of a single port.
-For example, to allow X11 connections, which use ports 6000-6007, use these commands:
+For example, to allow X11 connections, which use ports ''6000''-''6007'', use these commands:
-    sudo ufw allow 6000:6007/tcp
+<cli bash>
-    sudo ufw allow 6000:6007/udp
+frater@vulkan:$ sudo ufw allow 6000:6007/tcp
+Rule added
+Rule added (v6)
+frater@vulkan:$ sudo ufw allow 6000:6007/udp
+Rule added
+Rule added (v6)
+</cli>
 When specifying port ranges with UFW, you must specify the protocol (tcp or udp) that the rules should apply to. We haven’t mentioned this before because not specifying the protocol automatically allows both protocols, which is OK in most cases.
-Specific IP Addresses
-When working with UFW, you can also specify IP addresses within your rules. For example, if you want to allow connections from a specific IP address, such as a work or home IP address of 203.0.113.4, you need to use the from parameter, providing then the IP address you want to allow:
+==== Specific IP Addresses ====
-    sudo ufw allow from 203.0.113.4
+When working with UFW, you can also specify IP addresses within your rules. For example, if you want to allow connections from a specific IP address, such as a work or home IP address of ''123.45.67.89'', you need to use the from parameter, providing then the IP address you want to allow:
-Output
+<cli bash>
+frater@vulkan:$ sudo ufw allow from 123.45.67.89
 Rule added
+</cli>
-You can also specify a port that the IP address is allowed to connect to by adding to any port followed by the port number. For example, If you want to allow 203.0.113.4 to connect to port 22 (SSH), use this command:
+<WRAP center round info>
+you're getting only **ONE** ''rule added'' since you're specifying only IPv4 address on your rule.
+</WRAP>
-    sudo ufw allow from 203.0.113.4 to any port 22
-Output
+You can also specify a port that the IP address is allowed to connect to by adding to any port followed by the port number. For example, If you want to allow 123.45.67.89 to connect to port 22 (SSH), use this command:
+<cli bash>
+frater@vulkan:$ sudo ufw allow from 123.45.67.89 to any port 22
 Rule added
+</cli>
-Subnets
+==== Subnets ====
-If you want to allow a subnet of IP addresses, you can do so using CIDR notation to specify a netmask. For example, if you want to allow all of the IP addresses ranging from 203.0.113.1 to 203.0.113.254 you could use this command:
+If you want to allow a subnet of IP addresses, you can do so using CIDR notation to specify a netmask. For example, if you want to allow all of the IP addresses ranging from ''123.45.67.1'' to ''123.45.67.254'' you could use this command:
-    sudo ufw allow from 203.0.113.0/24
-Output
+<cli bash>
+frater@vulkan:$ sudo ufw allow from 123.45.67.0/24
 Rule added
+</cli>
-Likewise, you may also specify the destination port that the subnet 203.0.113.0/24 is allowed to connect to. Again, we’ll use port 22 (SSH) as an example:
+Likewise, you may also specify the destination port that the subnet ''123.45.67.0/24'' is allowed to connect to. Again, we’ll use port ''22'' (SSH) as an example:
-    sudo ufw allow from 203.0.113.0/24 to any port 22
-Output
+<cli bash>
+frater@vulkan:$ sudo ufw allow from 123.45.67.0/24 to any port 22
 Rule added
+</cli>
-Connections to a Specific Network Interface
+==== Connections to a Specific Network Interface ====
-If you want to create a firewall rule that only applies to a specific network interface, you can do so by specifying “allow in on” followed by the name of the network interface.
+If you want to create a firewall rule that only applies to a specific network interface, you can do so by specifying ''allow in on'' followed by the name of the network interface.
 You may want to look up your network interfaces before continuing. To do so, use this command:
-    ip addr
+<cli bash>
+frater@vulkan:$ ip addr
+: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
+:
+: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
+:
+</cli>
-Output Excerpt
+The output indicates the network interface names; they are typically named something like ''eth0'' or ''enp3s2''.
-: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
-. . .
-: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
-. . .
-The highlighted output indicates the network interface names. They are typically named something like eth0 or enp3s2.
+So, if your server has a public network interface called ''eth0'', you could allow HTTP traffic (port ''80'') to it with this command:
-So, if your server has a public network interface called eth0, you could allow HTTP traffic (port 80) to it with this command:
+<cli bash>
+frater@vulkan:$ sudo ufw allow in on eth0 to any port 80
-    sudo ufw allow in on eth0 to any port 80
-Output
 Rule added
 Rule added (v6)
+</cli>
 Doing so would allow your server to receive HTTP requests from the public internet.
-Or, if you want your MySQL database server (port 3306) to listen for connections on the private network interface eth1, for example, you could use this command:
+Or, if you want your MySQL database server (port ''3306'') to listen for connections on the private network interface ''eth1'', for example, you could use this command:
-    sudo ufw allow in on eth1 to any port 3306
+<cli bash>
+frater@vulkan:$ sudo ufw allow in on eth1 to any port 3306
-Output
 Rule added
 Rule added (v6)
+</cli>
 This would allow other servers on your private network to connect to your MySQL database.
-Step 6 — Denying Connections
+===== Denying Connections =====
 If you haven’t changed the default policy for incoming connections, UFW is configured to deny all incoming connections. Generally, this simplifies the process of creating a secure firewall policy by requiring you to create rules that explicitly allow specific ports and IP addresses through.
-However, sometimes you will want to deny specific connections based on the source IP address or subnet, perhaps because you know that your server is being attacked from there. Also, if you want to change your default incoming policy to allow (which is not recommended), you would need to create deny rules for any services or IP addresses that you don’t want to allow connections for.
+However, sometimes you will want to deny specific connections based on the source IP address or subnet, perhaps because you know that your server is being attacked from there. Also, if you want to change your default incoming policy to **allow** (which is not recommended), you would need to create ''deny'' rules for any services or IP addresses that you don’t want to allow connections for.
-To write deny rules, you can use the commands previously described, replacing allow with deny.
+To write ''deny'' rules, you can use the commands previously described, replacing ''allow'' with ''deny''.
 For example, to deny HTTP connections, you could use this command:
-    sudo ufw deny http
+<cli bash>
+frater@vulkan:$ sudo ufw deny http
-Output
 Rule added
 Rule added (v6)
+</cli>
-Or if you want to deny all connections from 203.0.113.4 you could use this command:
+Or if you want to deny all connections from 123.45.67.894 you could use this command:
-    sudo ufw deny from 203.0.113.4
+<cli bash>
+frater@vulkan:$ sudo ufw deny from 123.45.67.89
-Output
 Rule added
+</cli>
-In some cases, you may also want to block outgoing connections from the server. To deny all users from using a port on the server, such as port 25 for SMTP traffic, you can use deny out followed by the port number:
+In some cases, you may also want to block outgoing connections from the server. To deny all users from using a port on the server, such as port ''25'' for SMTP traffic, you can use ''deny out'' followed by the port number:
-    sudo ufw deny out 25
-Output
+<cli bash>
+frater@vulkan:$ sudo ufw deny out 25
 Rule added
 Rule added (v6)
+</cli>
 This will block all outgoing SMTP traffic on the server.
-Step 7 — Deleting Rules
+===== Deleting Rules =====
 Knowing how to delete firewall rules is just as important as knowing how to create them. There are two different ways to specify which rules to delete: by rule number or by its human-readable denomination (similar to how the rules were specified when they were created).
-Deleting a UFW Rule By Number
-To delete a UFW rule by its number, first you’ll want to obtain a numbered list of all your firewall rules. The UFW status command has an option to display numbers next to each rule, as demonstrated here:
+==== Deleting a UFW Rule By Number ====
-    sudo ufw status numbered
+To delete a UFW rule by its number, first you’ll want to obtain a numbered list of all your firewall rules. The UFW status command has an option to display numbers next to each rule, as demonstrated here:
-Numbered Output:
+<cli bash>
+frater@vulkan:$ sudo ufw status numbered
 Status: active
      To                         Action      From
      --                         ------      ----
-[ 1] 22                         ALLOW IN    15.15.15.0/24
+[ 1] 22                         ALLOW IN    15.15.15.0/24              # Allow SSH(22) only from 15.15.15.0 subnet
-[ 2] 80                         ALLOW IN    Anywhere
+[ 2] 80                         ALLOW IN    Anywhere                   # Allow unsecured http servicing
+</cli>
-If you decide that you want to delete rule number 2, the one that allows port 80 (HTTP) connections, you can specify it in a UFW delete command like this:
-    sudo ufw delete 2
+If you decide that you want to delete rule number ''2'', the one that allows port 80 (HTTP) connections, you can specify it in a UFW delete command like this:
-Output
+<cli bash>
+frater@vulkan:$ sudo ufw delete 2
 Deleting:
  allow 80
 Proceed with operation (y|n)? y
 Rule deleted
+</cli>
-This will prompt for a confirmation then delete rule 2, which allows HTTP connections. Note that if you have IPv6 enabled, you would want to delete the corresponding IPv6 rule as well.
+This will prompt for a confirmation then delete rule 2, which allows HTTP connections.
-Deleting a UFW Rule By Name
-Instead of using rule numbers, you may also refer to a rule by its human readable denomination, which is based on the type of rule (typically allow or deny) and the service name or port number that was the target for this rule, or the application profile name in case that was used. For example, if you want to delete an allow rule for an application profile called Apache Full that was previously enabled, you can use:
+<WRAP center round important>
+If you have IPv6 enabled, you would want to delete the corresponding IPv6 rule as well.
+</WRAP>
-    sudo ufw delete allow "Apache Full"
+==== Deleting a UFW Rule By Name ====
-Output
+Instead of using rule numbers, you may also refer to a rule by its human readable denomination, which is based on the type of rule (typically ''allow'' or ''deny'') and the service name or port number that was the target for this rule, or the application profile name in case that was used. For example, if you want to delete an ''allow'' rule for an application profile called ''Apache Full'' that was previously enabled, you can use:
+<cli bash>
+frater@vulkan:$ sudo ufw delete allow "Apache Full"
 Rule deleted
 Rule deleted (v6)
+</cli>
-The delete command works the same way for rules that were created referencing a service by its name or port. For example, if you previously set a rule to allow HTTP connections with sudo ufw allow http, this is how you could delete said rule:
+The ''delete'' command works the same way for rules that were created referencing a service by its name or port. For example, if you previously set a rule to allow HTTP connections with ''sudo ufw allow http'', this is how you could delete said rule:
-    sudo ufw delete allow http
-Output
+<cli bash>
+frater@vulkan:$ sudo ufw delete allow http
 Rule deleted
 Rule deleted (v6)
+</cli>
-Because service names are interchangeable with port numbers when specifying rules, you could also refer to the same rule as allow 80, instead of allow http:
+Because service names are interchangeable with port numbers when specifying rules, you could also refer to the same rule as ''allow 80'', instead of ''allow http'':
-    sudo ufw delete allow 80
-Output
+<cli bash>
+frater@vulkan:$ sudo ufw delete allow 80
 Rule deleted
 Rule deleted (v6)
+</cli>
+<WRAP center round info>
 When deleting UFW rules by name, both IPv4 and IPv6 rules are deleted if they exist.
-Step 8 — Checking UFW Status and Rules
+</WRAP>
+===== Checking UFW Status and Rules =====
 At any time, you can check the status of UFW with this command:
-    sudo ufw status verbose
+<cli bash>
+frater@vulkan:$ sudo ufw status verbose
+</cli>
 If UFW is disabled, which it is by default, you’ll see something like this:
-Output
+<cli bash>
 Status: inactive
+</cli>
-If UFW is active, which it should be if you followed Step 3, the output will say that it’s active and it will list any rules that are set. For example, if the firewall is set to allow SSH (port 22) connections from anywhere, the output might look something like this:
+If UFW is active, which it should be if you followed [[#allowing_ssh_connections|Allow SSH Connections]], the output will say that it’s active and it will list any rules that are set. For example, if the firewall is set to allow SSH (port 22) connections from anywhere, the output might look something like this:
+<cli bash>
 Output
 Status: active
@@ Ligne 332: / Ligne 421: @@
 --                         ------      ----
 /tcp                     ALLOW IN    Anywhere
+</cli>
 Use the status command if you want to check how UFW has configured the firewall.
-Step 9 — Disable or Reset Firewall
+===== Disable or Reset Firewall =====
 If you decide you don’t want to use the UFW firewall, you can deactivate it with this command:
-    sudo ufw disable
-Output
+<cli bash>
+frater@vulkan:$ sudo ufw disable
 Firewall stopped and disabled on system startup
+</cli>
-Any rules that you created with UFW will no longer be active. You can always run sudo ufw enable if you need to activate it later.
+Any rules that you created with UFW will no longer be active. You can always run ''sudo ufw enable'' if you need to activate it later.
 If you already have UFW rules configured but you decide that you want to start over, you can use the reset command:
-    sudo ufw reset
-Output
+<cli bash>
+frater@vulkan:$ sudo ufw reset
 Resetting all rules to installed defaults. This may disrupt existing ssh
 connections. Proceed with operation (y|n)? y
-Backing up 'user.rules' to '/etc/ufw/user.rules.20210729_170353'
+Backing up 'user.rules' to '/etc/ufw/user.rules.20241129_170353'
-Backing up 'before.rules' to '/etc/ufw/before.rules.20210729_170353'
+Backing up 'before.rules' to '/etc/ufw/before.rules.20241129_170353'
-Backing up 'after.rules' to '/etc/ufw/after.rules.20210729_170353'
+Backing up 'after.rules' to '/etc/ufw/after.rules.20241129_170353'
-Backing up 'user6.rules' to '/etc/ufw/user6.rules.20210729_170353'
+Backing up 'user6.rules' to '/etc/ufw/user6.rules.20241129_170353'
-Backing up 'before6.rules' to '/etc/ufw/before6.rules.20210729_170353'
+Backing up 'before6.rules' to '/etc/ufw/before6.rules.20241129_170353'
-Backing up 'after6.rules' to '/etc/ufw/after6.rules.20210729_170353'
+Backing up 'after6.rules' to '/etc/ufw/after6.rules.20241129_170353'
+</cli>
 This will disable UFW and delete any rules that were previously defined. This should give you a fresh start with UFW. Keep in mind that the default policies won’t change to their original settings, if you modified them at any point.
-Deploy your frontend applications from GitHub using DigitalOcean App Platform. Let DigitalOcean focus on scaling your app.
+===== Conclusion =====
-Conclusion
 Your firewall is now configured to allow (at least) SSH connections. Be sure to allow any other incoming connections that your server requires, while limiting any unnecessary connections, so your server will be functional and secure.
-To learn about more common UFW configurations, check out the UFW Essentials: Common Firewall Rules and Commands tutorial.

Nox-Rhea WiKi

Outils pour utilisateurs

Outils du site

Différences

Outils de la page