mima, to random

Permission-based systems are bad. See getting replaced by for example. It didn't stop from getting into the or the extension store. On the contrary, the malware problem only got worse after the complete replacement of XUL extensions, which is often disparaged as "insecure" because it allowed users to pretty much change how their browser fundamentally works.

Who knew that distrusting your users and not giving them control leads to more malicious software and user being broken more often. ​:seija_coffee:​

RE: https://mamot.fr/users/gnomelibre/statuses/112371181710549606

campuscodi, to random
@campuscodi@mastodon.social avatar

German police takes down StresserTech DDoS-for-hire service

noelreports, to random
@noelreports@mstdn.social avatar
JSharp1436,
@JSharp1436@mstdn.social avatar

@noelreports

We'll see

Those can still be screwed around with, like the and that were sent in terrible, almost unusable, condition

could quite easily instruct the to disable 1 in 4 to launch and 2 in 4 not detonating, leaving just 1 out of 4 working

He'll just say "we told you they were old" when in fact there's nothing wrong with any of them

has proven utterly untrustworthy as a Partner for AND European members

sordid, to random

Smart locks securing entry to an estimated 50,000 dwellings nationwide contain hard-coded credentials that can open them remotely.

https://web.archive.org/web/20240415235929/https://krebsonsecurity.com/2024/04/crickets-from-chirp-systems-in-smart-lock-key-leak/

The lock's maker Chirp Systems remains unresponsive, even though it was first notified about the critical weakness in March 2021. Meanwhile, Chirp's parent company, RealPage, Inc., is being sued by multiple U.S. states for allegedly colluding with landlords to illegally raise rents.

P.S. never give cybersecurity spooks clicks even after they go "freelance" or whatever

@latestagecapitalism

Morishima, to random
@Morishima@ieji.de avatar
nixCraft, to random
@nixCraft@mastodon.social avatar

Regarding xz-utils backdoor (liblzma5): Right now no Debian stable versions are known to be affected.
Compromised packages were part of the Debian testing, unstable and experimental distributions, with versions ranging from 5.5.1alpha-0.1 (uploaded on 2024-02-01), up to and including 5.6.1-1. The package has been reverted to use the upstream 5.4.5 code, which we have versioned 5.6.1+really5.4.5-1. Debian 12/11/10 appears safe. Taken from https://lists.debian.org/debian-security-announce/2024/msg00057.html

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • Hentai
  • doujinshi
  • announcements
  • general
  • All magazines