This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Install a newer kernel in Debian 9 (stretch) stable (sept 2017) | |
When using the latest version of Debian 9 stable, even with all updates installed, by default, you can’t get a very recent kernel via the standard repositories in your package manager. While the idea of using Debian stable is to remain stable and rather conservative, there are several benefits with installing a newer kernel and in some cases it’s the only option to get the OS to support all your hardware. The risk and impact on stability is small and the process is rather simple. | |
Some of the benefits are: | |
Support for previously unsupported hardware: every kernel release has a list of added drivers. Especially when you have recent hardware, a newer kernel could be required to fully support your video card for example. | |
Performance improvements and bug fixes: newer kernels often contain a lot of bug fixes, have new functions and performance tweaks. Here again, the most is to gain on newer hardware. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Unbound configuration file for Debian. | |
# | |
# See the unbound.conf(5) man page. | |
# | |
# See /usr/share/doc/unbound/examples/unbound.conf for a commented | |
# reference config file. | |
# | |
# The following line includes additional configuration files from the | |
# /etc/unbound/unbound.conf.d directory. | |
server: |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# 2 solutions to protect your Searx instance | |
- One way to protect Searx is using Filtron. | |
Filtron was written by the Searx author and acts as proxy between the webserver and the application. | |
- second way use fail2ban. | |
the jails: place them into "etc/fail2ban/filter.d" : | |
apache-searx-csv.conf: | |
# Fail2Ban configuration file |