Keyoxide: https://keyoxide.org/70d44f48bd35a7657aa524b06712beeaaf48a9d6
But microcode update can't fix CPUs that are already crashing or unstable.
![Intel has finally tracked down the problem making 13th- and 14th-gen CPUs crash](https://pawb.social/pictrs/image/4c3ebb16-2d0d-4f8e-b2c1-99965630c41f.jpeg?format=webp&thumbnail=256)
apparently intel has finally figured out why 13th and 14th gen CPU are failing. the issue is mainly caused by a faulty microcode algorithm, which causes the CPU requesting more voltage than it needs and results in oxidation issues within the chip itself.
CPU's that do not show any symptoms yet could be saved by a microcode update, but there is no real hope for those that already started to rust away
Threat actors are exploiting the massive business disruption from CrowdStrike's glitchy update on Friday to target companies with data wipers and remote access tools.
![Fake CrowdStrike fixes target companies with malware, data wipers](https://pawb.social/pictrs/image/63c1ee45-1c91-40bb-8f5d-2737471cbd56.jpeg?format=webp&thumbnail=256)
raise your paw if youre surprised that bad actors now distribute malware disguised as "crowdstrike fix / update"
love the quote at the end. there are far too many situations where windows is because "because!" where its just the wrong tool for the job. pos, web servers, trains to name a few i can think of...
Google Chrome has an API accessible only from *.google.com
So apparently Chrome ships with an extension that is invisible to the user, can not be disabled and allows any *.google.com
page to get detailed information about CPU and memory usage.
It is apparently at least 10 years old, was originally developed to debug Hangouts and people do claim that it is also shipped in Brave and Edge.
Who knows what else might be hidden in there!
Original Tweet: https://xcancel.com/lcasdev/status/1810696257137959018 Chrome Source: https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/resources/hangout_services/ Commit from October, 2013: https://github.com/chromium/chromium/commit/422c736b82e7ee763c67109cde700db81ca7b443
eggcelent news!
ye, dont think ive seen anyone talk about that. sad
wonderful read. ive reached a point where i can do nothing but lean back, sip a drink and laugh while these companies race each other to destroy their platforms. might as well start betting on who does the next stupid decision...
Archie has been resurrected
Some people have apparently not only gone through the trouble of digging out the latest available version of Archie (old FTP indexer / search engine from the mid 80's / 90's before Google was a thing), but they even set up a fresh install and made a web interface available. Even better: The entire source code apparently also still exists.
Video about said resurrection: https://piped.video/watch?v=CUwR9xdEuZI
breaking news: researchers discover that network protocols work as intended. mindlessly connecting to an untrusted network is still a bad idea.
to quote the article: "Do not use untrusted networks if you need absolute confidentiality of your traffic" or use HTTPS and a SOCKS5 proxy
yup yup yup. didnt steam also have some "fun" rm -rf bug a few years ago? proper backups and sandboxing go a long way
ok, after reading that article fully, it does sound a lot less concerning than the headline would like me to believe. it is early in the morning (almost 13:00) and this is a great chance to expose how little i know about all that, so i will:
They believed SSH traffic was immune [...].
classic. we always think that something is perfectly safe until it breaks. also, looking at the article, the issue with RSA has been known since 1996. there had to be a useful application for this. such as TLS. and now some SSH implementations.
Last year, researchers found that [...] they were still able to passively observe faulty signatures that allowed them to compromise the RSA keys of [...] Baidu.com
no idea how this adds any value in a discussion about SSH, but i chuckled.
now the article also get to some more interesting stats.
5.2 billion SSH records. of that 590k with invalid signatures and 4.9k revealed factorization for a total of 189 unique private keys.
now i would very much prefer that last number to be a solid zero, but out of 590k faults, only 4.9k were usable for the attack. everyone that thinks "oh thats nothing. im safe." is still a fool, but it could be far worse. especially since this only target RSA and leaves ed25519 (and others) untouched.
but it just gets even better:
The researchers traced the keys they compromised to devices that used custom, closed-source SSH implementations that didn’t implement the countermeasures found in OpenSSH and other widely used open source code libraries.
if i was drinking something reading this, i would have spat it out laughing. i am that kind of fun at parties. this also partially explains why there are "only" 590k invalid signatures in over 5.2 billion records total. and judging by how good some companies and organizations handle updates (assuming there will be updates from cisco, zyxel, hillstone and mocana), this will still be enough to be used in some attacks five years from now.
Wizz UH-U c16-1 7 d: One of the greenest moons ive ever seen
![](https://lemmy.world/pictrs/image/a2562e79-086c-45ba-9b07-474e4c891e1b.png?format=webp&thumbnail=128)
![](https://lemmy.world/pictrs/image/a2562e79-086c-45ba-9b07-474e4c891e1b.png?format=webp)
Almost everything looked green on there. The ice, the ship, the thin methane atmosphere and even the fonticulua. Absolutely breathtaking.
yep. and i wouldnt be surprised if that was intentional. how quickly they backed off on that one very much smells like a classic door in the face tactic. this whole WEI thing is far from being over
Recent picture of me standing on / inside of my exploration liner
![](https://lemmy.world/pictrs/image/cba8b616-e2eb-40a3-8398-086346594181.png?format=webp&thumbnail=128)
![](https://lemmy.world/pictrs/image/cba8b616-e2eb-40a3-8398-086346594181.png?format=webp)
Taken on Eocs Aip JC-D d12-1 3. May or may not be the start of a ~700kLy trip. Star distribution resembles more of a thin mist out here...
We'll take a look at how DJI - dominating player for commercial and recreational drones - builds their software, specifically from a secu...
![WTF DJI, UAV CTF?!](https://pawb.social/pictrs/image/79d2e75d-3a25-4ef0-b780-f7e24ad389a6.jpeg?format=webp&thumbnail=256)
If you don't like flying drones, treat them as hardware CTF's instead!
Chrome now ships with a user-tracking ad platform baked in
Chrome now directly tracks users, generates a "topic" list it shares with advertisers.
![Google gets its way, bakes a user-tracking ad platform directly into Chrome](https://pawb.social/pictrs/image/5d537d20-b6e1-487d-b92e-86ac5aa8585c.jpeg?format=webp&thumbnail=256)
Google's browser not only got new chrome, it now also uses keeps track of all websites you visit to generate a topic list for ads that is shared with websites directly. Nobody asked for that.
i honestly have so much trust into the whole music industry, and especially UMG, that id bet my best guillotine on this ending up to be absolutely detrimental to artists. if you have generative AI and can generate music for you, why even pay artists? sure sounds like the first step in that direction
During the past few years, many people have started to use virtualized eSIMs instead of the classic physical chip card SIMs. Behind the ...
![Demystifying eSIM Technology](https://pawb.social/pictrs/image/9440dacd-bcc0-4658-b506-7f0b79d37058.jpeg?format=webp&thumbnail=256)
a very interesting talk by Harald Welte about the complex mechanisms and architecture that keep eSIM working. prepare for a lot of acronyms
absolutely. a lot of currently in use public key schemes may be broken with those. more recently there have been a few newer algorithm such as kyber that do have a chance to hold. think NIST is also holding a bit of a competition, but dont quote me on that. i really dont know alot about post-quantum crypto
im honestly not really surprised anymore. i fully expect to see a lot more of these types of bugs in the coming years
Intel Arc drivers now ship with telemetry enabled by default
intel now joins the club with their take on GPU driver telemetry. they call it "Computing Improvement Program" and it can thankfully be disabled during a manual install, or in system settings after the installation is complete
and im already dreaming of the day all of those (sometimes really hard to work with) pseudocode "implementations" that are scattered across wikipedia will be replaced with immediately runnable, CC-0 licensed code. itll probably take years, but i do like the idea
hah. no. not on a platform where the lead thinks serving you a good dozen unskippable ads to test your patience is a fun little experiment. sure is the year of big platforms trying everything to get rid of users
In cases when viewers feel they have been falsely flagged as using an ad blocker, they can share this feedback by clicking on the link in the prompt.
and you can bet that ill (ab)use that. might as well make it just a bit harder for them
does look good. the more i get to use jebora, the more i honestly get annoyed with it. lots of rough edges. hope liftoff will be a worthy replacement
reading that just once again reminded me of how much requirements for those services can differ from person to person. especially that section about integrations. never threw money at spotify or youtube music fwiw