Repository navigation
v1.0.3 #25
FileBay
announced in
Announcements
v1.0.3
#25
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
What changed in 1.0.3
Slow storage no longer loses observations. On an SD card or other slow storage, writes could stall for seconds at a time, and whatever was being written was dropped. Now a write that hits a busy database is retried, and the capture pipeline holds a failed batch in memory and tries again, backing off to every 30 seconds while the storage is slow. The write-ahead log is folded back into the database on a timer instead of in the middle of a write, and the Docker health check no longer opens the database at all. Thanks to @tian-sigons for the report in #9.
A damaged database is now reported. If the database file is damaged, usually by failing storage, LAN Sheriff now says so: in a banner on the dashboard, in
/api/health, and throughlan-sheriff health, which exits 1. All three say how to fix it. A full check of the database runs a minute after start and every six hours after that. Before, the damage only showed up as warnings in the log while the Wanted List quietly stopped growing.A new malware list. URLhaus retired its free downloads, so new installs, including fresh Docker containers, were starting with no malware list at all, and the threat list rule could never fire. It is replaced with the HaGeZi Threat Intelligence Feed (the mini edition, about 200,000 domains, refreshed by HaGeZi every few hours). A domain on both the malware list and the ad list is now labelled malware; before, the ad list won. Expect about 15 MB more memory.
One rare-destination finding per device. A device that reaches unusual countries now raises a single finding that lists them, instead of one per country. Findings from earlier versions are merged on upgrade without notifying you again.
Four new languages. Italian, Korean, Polish and Ukrainian, for sixteen in all. They have not yet been reviewed by native speakers; corrections are welcome.
Smaller fixes.
.arpa) by default. Tick "Show reverse lookups" to see them. Search and export are not filtered.Security
golang.org/x/net0.62.0,golang.org/x/crypto0.58.0 andgopacket1.7.2.Changes to know about
lan-sheriff health. It asks a running instance whether it is alive and exits 0 if so. The Docker health check now uses it. Write stalls are reported but do not fail it; a damaged database does. It asks127.0.0.1:2911unless you pass--url./api/healthanswers without a password. It reports whether the server is up, whether writes are landing and whether the database is damaged. It contains nothing that was observed, and it does not reveal where your data is stored.lan-sheriff statusno longer writes. It now opens the database read-only, so it never creates or migrates one. It exits 1 if there is no database. On a database from before 1.0.3, runlan-sheriff serveonce first.--notify-min-scorethreshold.This discussion was created from the release v1.0.3.
All reactions