Mozilla updates Firefox’s Terms of Use after user concerns over data rights.

The new revisions clarify that Mozilla doesn’t own your data—but the language change follows a wave of community criticism.

Read the full breakdown here: https://thehackernews.com/2025/03/mozilla-updates-firefox-terms-again.html

Microsoft is finally shutting down Skype in May

https://www.xda-developers.com/microsoft-killing-skype/

‘You Can’t Hide’: #Elon #Musk & #SpaceX Are Helping US Intelligence Build the World’s Largest Spy Satellite Network

Why are so many freedom loving, privacy aware people using a military contractor’s satellite service, and turning a blind eye to the surveillance grid he is co-creating with the U.S. military and intelligence?

https://www.thelastamericanvagabond.com/musk-space-x-satellite-network/

"Haunted by Legacy: Discovering and Exploiting Vulnerable #Tunnelling Hosts", 2025.

This paper is the first to systematically analyse the securityof tunnelling hosts on the IPv4 and IPv6 Internet. Our large-scale Internet-wide scans identified over 4 million hosts that
accept unencrypted tunnelling packets from any source.

This is concerning because vulnerable hosts can be abused asone-way proxies, and many of these hosts also allow an ad-versary to spoof a packet’s source address, enabling variouskinds of known and novel attacks.

Moreover, we also demon-strated that these vulnerable hosts enable novel DoS attacks,such as our TuTL and Ping-Pong attacks. The TuTL attack
is especially concerning since it can be abused to perform DoS attacks against any third-party host on the Internet.

Our measurements also show that many Autonomous Systems,more than four thousand in total, do not (properly) imple-ment source address filtering, thereby allowing the spoofing
of source IP addresses.

#Hosts #Vulnerability

📱 Scam by Apple as it created a plain-text protocol and said it protects user privacy.

The nature of SORM as a surveillance system built directly into telecommunications and internet infrastructure facilitates potential interception of a vast range of data and significantly reduces visibility into digital surveillance operations, almost certainly raising the risk of abuse for countries that have
historically conducted intrusive domestic surveillance with limited oversight.

As SORM provider VAS Experts notes, “the person who is being monitored cannot in any way determine that this is happening, just as the [service] provider does not know who the special service is following”.

In this, identifying deployments of SORM becomes more difficult compared to commercial off-the-shelf spyware tools,
such as Predator, which can be identified and traced via changes in infrastructure.

#SORM

Hackers exploit 16 zero-days on first day of Pwn2Own Automotive 2025
https://www.bleepingcomputer.com/news/security/hackers-exploit-16-zero-days-on-first-day-of-pwn2own-automotive-2025/

AMD reveals AMDGPU Composition Stack, a fork of Wayland's Weston compositor for advancing the Linux desktop | GamingOnLinux
https://www.gamingonlinux.com/2025/01/amd-reveals-amdgpu-composition-stack-a-fork-of-waylands-weston-compositor-for-advancing-the-linux-desktop/

g.co, Google's official URL shortcut, is compromised
(update: or Google Workspace's domain verification, see bottom) People are actively having their Google accounts stolen.

https://gist.github.com/zachlatta/f86317493654b550c689dc6509973aa4

Comments

CarCareKiosk – Free How-to Videos to Fix Your #Cars

https://www.carcarekiosk.com

#Android #web #browsers

Ungoogled Chromium (forked from cromite) with Bromite patches and additional codecs
https://github.com/macchrome/droidchrome/releases
https://chromium.woolyss.com/#android

Cromite is another example of ungoogled chromium without the extra codecs from the above link, but cromite includes more patches as noted at github.
https://github.com/uazo/cromite
Fdroid repo
https://www.cromite.org/fdroid/repo?fingerprint=49f37e74dee483dca2b991334fb5a0200787430d0b5f9a783dd5f13695e9517b

For an Android Firefox based browser, use IronFox
https://gitlab.com/ironfox-oss/IronFox/-/releases
Fdroid repo
https://fdroid.ironfoxoss.org/fdroid/repo?fingerprint=c5e291b5a571f9c8cd9a9799c2c94e02ec9703948893f2ca756d67b94204f904

These can be added to Obtainium to download the latest release when they are available
https://github.com/ImranR98/Obtainium

https://archive.is/0OLMG

how to change #linux machine-id

#Linux devices have a unique identifier called machine-id. Here is how to change it.

Posted on February 24, 2021

What is a machine-id, and why should you randomize it? From the machine-id man pages, it is defined as:

This ID uniquely identifies the host. It should be considered “confidential”, and must not be exposed in untrusted environments, in particular on the network. If a stable unique identifier that is tied to the machine is needed for some application, the machine ID or any part of it must not be used directly.
https://www.man7.org/linux/man-pages/man5/machine-id.5.html

In an effort to promote privacy, having a unique and unchanging identifier tied to your device seems like the wrong approach. It’s quite possible that poorly coded or even maliciously coded software could fetch this ID from your system. Let’s make sure that even if that does happen, that the value is constantly changing so that your device can not be uniquely identified as your device.
This is an incredibly simple and quick adjustment to your default Linux system. What we’re doing is showing you how to either adjust this value manually by hand, or by running a cronjob to change this value every minute with a new, randomized value.
Before we begin, a disclaimer: We’ve tested this on our own work desktops and development environments and I’ve tested it on my daily driver desktop. We have not found that anything has ‘broken’ because of this, but this is untested in many environments and may not be suitable for your use. It’s always reversible if you later wish to continue with a single, uniquely identifying ID attached to your device(s).
Debian / Ubuntu systems
To check your machine-id, open up your terminal and enter the following:
cat /etc/machine-id
The output should look a little something like this:
a9976154f0084a3782892638656ad9fd
You’ll note that this value is also stored in /var/lib/dbus/machine-id and that a symlink between the two exist. Any change to one file, will be reflected in the other.
me@virtbox-testing:~$ cat /etc/machine-id a9976154f0084a3782892638656ad9fd me@virtbox-testing:~$ cat /var/lib/dbus/machine-id a9976154f0084a3782892638656ad9fd
If you reboot your device, you’ll notice that this value remains unchanged. So, let’s change it ourselves!
Method 1: Manually.
Method 2 is automatically, every minute, as ran by a cron-job. If you don’t want to fully commit to that, you can change your machine-id by hand manually whenever you feel like it.
Step 1, remove the old machine-id file.
sudo rm /etc/machine-id
Step 2, recreate the machine-id file.
sudo systemd-machine-id-setup
Step 3, confirm that /etc/machine-id (and /var/lib/dbus/machine-id) now show a new value, different from the original.
cat /etc/machine-id && cat /var/lib/dbus/machine-id
That’s it! You should see two lines in your output with matching IDs that differ from the original machine-id you had in the beginning.
me@virtbox-testing:~$ cat /etc/machine-id && cat /var/lib/dbus/machine-id a78badce3e73beced163bbef7e55232a a78badce3e73beced163bbef7e55232a
You’ve changed your device’s uniquely identifying machine-id. This change will survive device reboots and will remain the same until you create a new one.
Method 2: Changing every 1 minute, automatically.
If the above didn’t satisfy your needs, than feel free to automate the creation of a new machine-id by creating a cronjob entry that will generate a new ID every minute.
Step 1, open up your crontab file.
sudo crontab -e
Step 2, enter at the bottom of the file the following:
*/1 * * * * sudo rm /etc/machine-id && sudo systemd-machine-id-setup
Save and Exit.
Step 3, wait a minute and confirm that your machine-id value has changed:
cat /etc/machine-id && cat /var/lib/dbus/machine-id
You should see two new matching values, that differs from the original value you had at the start. Wait a minute and run the step 3 command again, and you’ll see that these values have changed.

You’ll see that the command, when ran a minute or more apart, will produce new values now.
me@virtbox-testing:~$ cat /etc/machine-id && cat /var/lib/dbus/machine-id b722903d87994e24b6378289262c3021 b722903d87994e24b6378289262c3021 me@virtbox-testing:~$ cat /etc/machine-id && cat /var/lib/dbus/machine-id 4352c41ad7fb4a05a54b0942c5c27cb0 4352c41ad7fb4a05a54b0942c5c27cb0
In closing
Uniquely identifying ID’s are rarely a good thing when you take privacy into consideration, and although these items have their purpose in limited use cases it doesn’t appear that generating a new unique ID every minute has any downsides.
What do you think? Is this a pointless privacy practice or a needed, but often overlooked part in maintaining privacy in the modern age? Let us know in the comments below.
Additional Thoughts
After publishing this article, we received some feedback that I’d like to touch base on here.
Testing the high privacy, pro-anonymity Tails-OS shows that you receive a new machine-id after every reboot. Props to Tails-OS!
Testing the privacy and anonymity promoting Whonix-OS shows that they do not issue a new machine-ID after every reboot.
A commenter on a [RAMBLE] post mentions that MXLinux does not use systemd, and thus does not use a machine-id.
Here is a list of Linux operating systems that do not use systemd. (And will not have a machine-id)
Yes, there are other uniquely identifying aspects on all systems. From device serial numbers to MAC addresses. The purpose of this post was to discuss a lesser discussed unique identifer: machine-id.

119 #Vulnerabilities In LTE #5G Core Infrastructure