OP tagged Linux in the post and that specific tag actually links to !linux@lemmy.ml resulting in the Mastodon post being posted to the community
OP tagged Linux in the post and that specific tag actually links to !linux@lemmy.ml resulting in the Mastodon post being posted to the community
Anyone that still wants a supported version of win 10, look into Windows 10 IoT Enterprise LTSC (2021) - supported until 2032 and can be activated by MAS with HWID
I thought running
rm -rf /dev/*
was a good idea, I was sure worst case scenario […]
Worst case scenario:
You should be able to update the config file for SearXNG to add the port to the URL. Then just restart SearXNG; removing and re-adding the search engine to Firefox should make sure it’s updated to use the correct port.
In the settings.yml file, under the server:
section is the setting you want to change:
base_url: http://192.168.1.65:8887/
Leave port:
unchanged
Looks like the 5.6.1-2 release on Arch moved from using the published GitHub releases to just using the git repository directly, which as I understand avoids the exploit (because the obfuscated script to inject the exploit is only present in the packaged tarballs and not the git repo itself)
https://gitlab.archlinux.org/archlinux/packaging/packages/xz/-/commit/881385757abdc39d3cfea1c3e34ec09f637424ad