Diferències

Ací es mostren les diferències entre la revisió seleccionada i la versió actual de la pàgina.

Enllaç a la visualització de la comparació

--- linux:seguridad:sadservers [15/05/2024 06:58] – ["Saskatoon": counting IPs.] mate
+++ linux:seguridad:sadservers [28/05/2024 06:51] (actual) – ["Resumable Server": Linux Upskill Challenge] mate
@@ Línia 61: / Línia 61: @@
 == "The Command Line Murders"
+  * ''knock localhost 3000''
+  * ''nmap -p- localhost''
+<code>
+. You can use the knock utility, for example to knock on port 3000: knock localhost 3000. Netcat (nc) and nmap are also available. Note than nmap has some options where you'd need to be root (not possible here)
+. You can also write a BASH script that knocks sequentially on all ports.
+. Solution.Probably the fastest is using nmap against all ports, for example: nmap -p- localhost.
+</code>
+== "Resumable Server": Linux Upskill Challenge
 <code></code>
+== "Bucharest": Connecting to Postgres
+  * ''sudo systemctl restart postgresql@13-main''
+<code>
+. The issue might be related to the configuration of the PostgreSQL server. (See the error message when attempting the tedt). The configuration files are usually located in the /etc/postgresql/$version/main/ directory. You might want to start by checking these files. (You'll need to use "sudo").
+. The pg_hba.conf file controls client authentication. This file is read on start-up and when the main server process receives a SIGHUP signal. If you’re having trouble connecting to the database, this file could be a good place to look. (Click again "Next Clue/Solution" to reveal the final step)
+Solution: In the /etc/postgresql/13/main/pg_hba.conf file, delete or comment out the lines with a reject keyword from all. Then restart the PostgreSQL service: sudo systemctl restart postgresql@13-main
+</code>