âI allowed FireDragon to use the code for free.â
but ⌠closed source 
7 Likes
Thatâs an odd shift to say the least. Closed source Firefox browsers seem a bit silly to me, and there really hasnât been many in the past from what I have seen (Maybe like one or two that I can faintly remember? One being a multi-core browser that was only for Windows).
That really puts things in a weird spot now 
. A lot of the wording on that announcement makes it sound like they arenât too sure how they want things to be. Floorp might be up for a lot of âflip-floppingâ whenever it suits them.
Either way how it turns out, it leaves a bad taste in my mouth and makes it hard to care whatever the ânew featuresâ they are talking about in the new version if they are closed source.
(Looking foward to Waterfoxâs new features that are currently in beta at least 
)
7 Likes
The plot thickens, it seems:
Although the blog post announcing the code would be closed off was released only earlier today, it appears the âprivateâ repo linked in the post is now a public repository.
Now the code is licensed as CC BY-NC-SA (see: CC BY-NC-SA 4.0 Deed | Attribution-NonCommercial-ShareAlike 4.0 International | Creative Commons), which means people can use the code as they wish as long as they give credit to the author and donât use it for commercial purposes. So, people canât fork the browser and sell their fork (which I think may have been happening with the original license).
I think this seems like a reasonable choice. Probably they could have shifted to this license in a less disruptive way to avoid the backlash from the community, but câest la vie.
Meanwhile, it looks like the maintainer of the NixOS package is dropping it since it was announced that there will be proprietary bits:
I wonder if they will reconsider this move now that the author appears to be quickly backpedaling back to an open source model.
SoâŚthis is good! 
âŚI think?
6 Likes
I think its a crazy world we live inâalways wasâits just that sometimes smth. like this brings it to our attention. I also think that if we here lived only in the Windows World, we would never even notice news like this.
Does this mean weâre the âsensitiveâ type? 
5 Likes
âThis campaign is a prime example of the sophisticated tactics employed by malicious actors to distribute malware through trusted platforms like PyPI and GitHub,â the researcher concluded.
âThis incident highlights the importance of vigilance when installing packages and repositories even from trusted sources. It is crucial to thoroughly vet dependencies, monitor for suspicious network activity, and maintain robust security practices to mitigate the risk of falling victim to such attacks.â
5 Likes
Some interesting gaming related newsâŚ
6 Likes
All of Floorpâs source code is now publicly available once again!
To defend against these botnets, use strong admin passwords and upgrade your deviceâs firmware to the latest version that addresses known flaws. If the device has reached EoL, replace it with an actively supported model.
Common signs of malware infection on routers and IoTs include connectivity problems, overheating, and suspicious setting changes.
12 Likes
Meanwhile Tiktok is the one getting banned.
2 Likes
7 Likes
I was reading through Fedora 40 changes and came across these security enhancements.
I wonder if we could add some of these features in Garuda?
-
The NetworkManager gets a new ability to address conflicts of duplicate IPv6 addresses in the same physical network.
-
While this is something enabled by default under-the-hood, it should reduce unnecessary connectivity issues.
-
In terms of security, Fedora 40 decides to enable high level systemd security hardening settings. It aims to isolate and sandbox system services for enhanced protection.
-
And, not to forget, Fedora 40 randomizes the Mac addresses for each Wi-FIi connection with a stable/individual address to reduce passive surveillance by Internet Service Providers. So, giving you a better network privacy.
1 Like
Have you guys seen this? 
5 Likes
5 Likes
Malicious backdoor found in ssh libraries
https://openwall.com/lists/oss-security/2024/03/29/4
7 Likes
I never leave ssh or any type of remote access enabled. Most people would call that paranoid, but just because your paranoid doesnât mean they arenât out to get you. Usually my paranoia is justified, as backdoors have been found more than once in remote access software.
Also no wifi or bluetooth access on my computer or phone for me. Bluetooth is riddled with security holes, and wifi can be compromised especially if you use public connections.
7 Likes
I like to use Bluetooth headsets while travelling, but Iâve recently switched to a dedicated mp3 player for that purpose. Otherwise, my Bluetooth is always off, partially because of the reasons you mentioned. Additional reason to keep BT off at all time while using an iPhone: after each and every OS update Apple has suddenly turned BT back on. 
4 Likes
The situation only looks more bleak over time with how the upstream project was compromised while now the latest twist is GitHub disabling the XZ repository in its entirety.
The central repository tukaani-project/xz on GitHub has now been disabled by GitHub with the message:
âAccess to this repository has been disabled by GitHub Staff due to a violation of GitHubâs terms of service. If you are the owner of the repository, you may reach out to GitHub Support for more information.â
Arch Linux
The following release artifacts contain the compromised xz:
installation medium 2024.03.01
virtual machine images 20240301.218094 and 20240315.221711
container images created between and including 2024-02-24 and 2024-03-28
The affected release artifacts have been removed from our mirrors. We strongly advise against using affected release artifacts and instead downloading what is currently available as latest version! It is strongly advised to do a full system upgrade right away if your system currently has xz version 5.6.0-1 or 5.6.1-1 installed.
Following that were more clean-ups and fixes to the SRSO mitigation code. Itâs been a quiet few months since while merged on Friday was fixing some of the mitigation code due to being ineffective.
Thanks in part to that opt-in automatic crash reporting, details were gathered for fixing at least three important crashes within Plasma 6 this week.
5 Likes
3 Likes
4 Likes
9 Likes
No words 
The plot twist
I â â â â ing fell for it 
8 Likes