Historically, the MD5 checksums in our LFS files serve as a protection
against broken downloads, or accidentally corrupted source files.
While the sources are nowadays downloaded via HTTPS, it make sense to
beef up integrity protection for them, since transparently intercepting
TLS is believed to be feasible for more powerful actors, and the state
of the public PKI ecosystem is clearly not helping.
Therefore, this patch switches from MD5 to BLAKE2, updating all LFS
files as well as make.sh to deal with this checksum algorithm. BLAKE2 is
notably faster (and more secure) than SHA2, so the performance penalty
introduced by this patch is negligible, if noticeable at all.
In preparation of this patch, the toolchain files currently used have
been supplied with BLAKE2 checksums as well on
https://source.ipfire.org/.
Cc: Michael Tremer <michael.tremer@ipfire.org>
Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
Acked-by: Michael Tremer <michael.tremeripfire.org>
Bumping across one of our scripts with very long trailing whitespaces, I
thought it might be a good idea to clean these up. Doing so, some
missing or inconsistent licence headers were fixed.
There is no need in shipping all these files en bloc, as their
functionality won't change.
Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
* Add a Summary and Services field to all pak lfs files
* Replace occurances of INSTALL_INITSCRIPT with new INSTALL_INITSCRIPTS
macro in all pak lfs files.
Signed-off-by: Robin Roevens <robin.roevens@disroot.org>
Reviewed-by: Peter Müller <peter.mueller@ipfire.org>
- Update from 0.99.3 to 1.3
- No update required to rootfile
- perl-File-Tail is a dependency of the swatch addon
- Changelog
1.0 Actually just two minor bug fixes (one of them in a test), but I no
longer see a point in not having a 1.0 version.
1.1 Lee Duncan drew my attention to Stephan Muller's fixes for Windows compatibility
Changed the use of the system's mv command to using File::Copy in the
tests. (Steffen Mueller)
Added machine-readable license statement to Makefile.PL and thus
META.yml (Steffen Mueller)
The sixth test in 10/open.t is skipped on win32 because you can't just
move files around that are opened. (Steffen Mueller)
Due to using sysread and friends, there were newline problems on win32.
That should be fixed now. (Steffen Mueller)
1.2 Break the infinite loop that can result when the average length of lines
causes the attempt to fill the tail buffer to fill with the exact same
or even smaller number of lines.
1.3 Fix for a stupid bug in 1.2 (GFILATOV, Slaven_Rezic)
Added a warning for use of debug in a non-debug version of File::Tail
Shows a warning when maxbuf is set to a too-small value
Invoking name_changes callback changes the value of input attribute (sottile@ix.netcom.com)
When deciding to reopen the file, check if the inode matches (that would mean it has not
been ranamed)
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Not sure why this has ever been there. This simply makes it
nicer to read and edit because we can have line-breaks now.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f@ipfire.org>
Most of these files still used old dates and/or domain names for contact
mail addresses. This is now replaced by an up-to-date copyright line.
Just some housekeeping... :-)
Signed-off-by: Peter Müller <peter.mueller@link38.eu>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
http://sourceforge.net/projects/swatch/
With swatch you can easily monitor (growing) log files
in realtime and create email alerts based on log file content.
e.g. with a config file like this:
watchfor /Priority\: ([1|2])/
echo=normal
mail=alerts@your.domain,subject=[SNORT] Priority $1 Alert
and a swatch command like this:
swatch --daemon -c /var/ipfire/snort/swatchrc --input-record-separator='\n\n' -t /var/log/snort/alert
you can setup email alerts for SNORT alerts.
This still needs an active MTA (e.g. dma or postfix).
