The crude loop I wrote to come up with this changeset:
find -L package/feeds/packages/ -name patches | \
sed 's/patches$/refresh/' | sort | xargs make
Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* fix search string/pipe preparation for the background service
* fix IPSet maxelem limitation, made it more flexible
* fix potential error during resume action
* add Cisco Talos IP blacklist
* update readme
Signed-off-by: Dirk Brenken <dev@brenken.org>
We should be using "00" to deal with alphabetical order.
Fixes: e9a126c145 ("rng-tools: start as early as possible")
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Raspberry Pi devices (bcm2708) need this to get from:
[ 102.310494] random: crng init done
to:
[ 12.539744] random: crng init done
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Bugs:
- Fix SSH hostname parsing when it contains leading 's', 'h', and remove the quiet
option that was hiding the error (via docker-py bump to 4.4.2)
- Fix key error for --no-log-prefix option
- Fix incorrect CLI environment variable name for service profiles: COMPOSE_PROFILES
instead of COMPOSE_PROFILE
- Fix fish completion
Miscellaneous:
- Bump cryptography to 3.3.2
- Remove log driver filter
Signed-off-by: Javier Marcet <javier@marcet.info>
Currently when trying to build this package a build error is produced:
WARNING: 'automake-1.16' is missing on your system.
You should only need it if you modified 'Makefile.am' or
'configure.ac' or m4 files included by 'configure.ac'.
The 'automake' program is part of the GNU Automake package:
<https://www.gnu.org/software/automake>
It also requires GNU Autoconf, GNU m4 and Perl in order to run:
<https://www.gnu.org/software/autoconf>
<https://www.gnu.org/software/m4/>
<https://www.perl.org/>
This error is due to an attempt to use the native host tools instead of
the OpenWrt build system generated ones. By re-adding PKG_FIXUP it is
ensured that the correct version of the host tools are used.
Signed-off-by: Etan Kissling <etan_kissling@apple.com>
* add scanning for suspicious nginx events
* add a log counter to track the number of the failed requests
or login repetitions of the same ip in the log before banning,
defaults are: ssh (3), luci (3), nginx (5)
* optimize the background service handling
* add 'greensnow' as a new source
* update readme and LuCI frontend regarding the new log count options
Signed-off-by: Dirk Brenken <dev@brenken.org>
As suggested by others, I would like to take care of this tool. I am
developing certain tools that rely on the library and also owipcalc.
Signed-off-by: Nick Hainke <vincent@systemli.org>