• Home
• About
• Contact
• Disclaimer
• Privacy Policy

5.10.213: longterm

Posted: 2024-03-15 19:02:07
Source: http://www.kernel.org/

5.15.152: longterm

Posted: 2024-03-15 18:59:39
Source: http://www.kernel.org/

6.1.82: longterm

Posted: 2024-03-15 18:56:53
Source: http://www.kernel.org/

6.6.22: longterm

Posted: 2024-03-15 18:54:37
Source: http://www.kernel.org/

6.7.10: stable

Posted: 2024-03-15 18:52:28
Source: http://www.kernel.org/

6.8.1: stable

Posted: 2024-03-15 18:46:21
Source: http://www.kernel.org/

SQL Subtract

Posted: 2024-03-15 17:34:16
Source: https://linuxhint.com/sql-subtract/

Practical guide on how to use the SQL Subtract feature and how it can help us when working with relational databases using the NOT IN operator using examples.

SQL Select All Except

Posted: 2024-03-15 17:21:34
Source: https://linuxhint.com/sql-select-all-except/

Practical tutorial on all the methods to select all rows and columns from a given database table except the specific ones by utilizing various SQL techniques.

SQL Outer Join

Posted: 2024-03-15 17:16:06
Source: https://linuxhint.com/sql-outer-join/

Practical guide on understanding OUTER JOINS, what an OUTER JOIN is in SQL, the types of OUTER JOINS, and the examples of how to use these types of OUTER JOINS.

Case Insensitive SQL LIKE Operator

Posted: 2024-03-15 17:06:31
Source: https://linuxhint.com/sql-like-case-insensitive/

Practical guide on how to use the LIKE operator in Standard SQL you to check if a value is in a given set of values and perform a case insensitive comparison.

SQL Lead Function

Posted: 2024-03-15 17:01:25
Source: https://linuxhint.com/sql-lead-function/

Comprehensive tutorial on how to work with the lead() function to access the next item/row from the current row at a specific offset along with examples.

SQL Lag

Posted: 2024-03-15 16:55:21
Source: https://linuxhint.com/sql-lag/

Comprehensive guide on how to work with the SQL lag() function to get or access the previous item from the current row at a specific offset along with examples.

How to Connect to WiFi Network from the Command-Line on Linux Using NetworkManager

Posted: 2024-03-15 16:44:35
Source: https://linuxhint.com/connect-wifi-network-command-line-linux-networkmanager/

Tutorial on how to connect to your WiFi network from the command line on modern Linux distributions using the NetworkManager to manage the network devices.

Emacs Close Buffer

Posted: 2024-03-15 16:33:59
Source: https://linuxhint.com/emacs-close-buffer/

Tutorial on the common ways of closing the buffers in Emacs by closing the default buffer, closing the buffers interactively, and closing a specific buffer.

KDE neon 20240312 overview | The latest and greatest of KDE community

Posted: 2024-03-15 16:15:50
Source: https://www.youtube.com/watch?v=Vxv6UlC1qqc

Distribution Release: Void 20240314

Posted: 2024-03-15 12:40:29
Source: https://distrowatch.com/12084

The DistroWatch news feed is brought to you by TUXEDO COMPUTERS. The Void project produces an independent, rolling release Linux distribution. The project's latest snapshot provides a keyboard layout selector on the login screen, enables the chrony network time daemon, and supports Raspberry Pi 5 computers. The distribution's release announcement shares the details: "Some highlights of this release: A....

next-20240315: linux-next

Posted: 2024-03-15 03:04:27
Source: http://www.kernel.org/

KDE Plasma 6 Unleashed: A Fresh Look At New Enhancements & Features

Posted: 2024-03-15 02:30:54
Source: https://www.youtube.com/watch?v=Gyv-B1GX4K4

Distribution Release: Univention Corporate Server 5.0-7

Posted: 2024-03-14 16:03:25
Source: https://distrowatch.com/12083

The DistroWatch news feed is brought to you by TUXEDO COMPUTERS. Univention Corporate Server (UCS) is an enterprise-class distribution based on Debian GNU/Linux. The project has published an update to its 5.0 series which introduces blocklists for the Univention Directory Manager. "A new feature in UCS is “blocklists” for the Univention Directory Manager (UDM). This feature allows UDM to....

Secure A Multi-Server Security Engine Installation With HTTPS

Posted: 2024-03-14 16:00:00
Source: https://www.linuxjournal.com/content/improve-crowdsec-multi-server-installation-https-between-agents

by Manuel Sabban

Welcome to the second part of our tutorial on how to set up and secure a multi-server CrowdSec Security Engine installation. In the first part, I walked you through the setup of CrowdSec Security Engines across multiple servers, with one server serving as the parent and two additional machines forwarding alerts to it.

In this part, I will address security issues posed by clear HTTP communication in the previous multi-server Security Engine installation. To solve this, I propose establishing the communication between Security Engines over encrypted channels. This solution allows server-2 or server-3 to trust the server-1 identity and avoid man-in-the-middle attacks.

Using self-signed certificates

Create the certificate

First, you need to create a certificate. This can be achieved with the following one-liner.

bash
openssl req -x509 -newkey rsa:4096 -keyout encrypted-key.pem -out cert.pem -days 365 -addext "subjectAltName = IP:172.31.100.242"

For now, the Security Engine is not able to ask for the passphrase of the private key when starting. So, you have the choice to decipher the private key by hand each time you start or reload the Security Engine or store the key unencrypted. In any way, to strip the passphrase, you can use the following:

bash
openssl rsa -in encrypted-key.pem -out key.pem

Then, the unencrypted key file can be safely deleted after the Security Engine is started.

Configure the Security Engine to use a self-signed certificate

On server-1, you need to configure the Security Engine to use the generated certificate. As seen below, the tls.cert_file and tls.key_file options in the api.server section of the following /etc/crowdec/config.yaml excerpt is set to the generated certificate file.

yaml
api:
  server:
    log_level: info
    listen_uri: 10.0.0.1:8080
    profiles_path: /etc/crowdsec/profiles.yaml
    online_client: # Crowdsec API credentials (to push signals and receive bad 

    tls:
      cert_file: /etc/crowdsec/ssl/cert.pem
      key_file: /etc/crowdsec/ssl/key.pem

On the client side, configuration changes happen in two files. First, modify /etc/crowdec/config.yaml to accept self-signed certificates by setting the insecure_skip_verify to true.

You also need to change HTTP for HTTPS in the /etc/crowdsec/local_api_credentials.yaml file in order to reflect the changes. This small change has to be done on all three servers (server-1, server-2, and server-3).

Go to Full Article