It probably has a large database of exploits it can use. The article claims 20k, but this seems to high for me.
It probably has a large database of exploits it can use. The article claims 20k, but this seems to high for me.
Yes, but they replace common tools like top or lsof with manipulated versions. This might at least trick less experienced sysadmins.
Edit: Some found out about the vulnerability by ressource alerts. Probably very easy in a virtualized environment. The malware can’t fool the hypervisor ;)
I agree, but I understood this question in the context of a homelab.
And for me, a homelab is not the right place for a public website, for the reasons I mentioned.
No, with these reasons:
I have a VPS for these tasks, and I host a few sites for friends amd family.
I got it a few times over the last years, once on the steam deck.
By supporting work on a freelance basis
This sounds like Valve is paying devs to work full time on arch, and thus managing to achive more than volunteers could.
You’re right, my comment was oversimplified.
Because both ways are used. Microsoft relies on file names, linux on the first bytes of the file.
I don’t think “most” applies here. Text-based files, pdf, media files and most executeable files are not .zip.
I think it makes sense from a programming view. When you have a document, you can add all the media files and pack them together as one archive. Then the program sets the filename to .docx so everyone knows that they need an office program to open that file.
For the users, all you need to know is what program can open which files. If every document would be named .zip, you would have no idea if it was a spreadsheet or slides for your presentation.
OP refers to the fact that you can rename some filetypes to .zip and unpack them.
Notable examples microsoft office files (.docx) or android apps (.apk).
Counterexample are media files (mp3, mp4, jpg).
I was a little disappointed how little happens. Anybody still remember the baseball at the speed of light?
Thanks for the hint on nVidia. That might explain my issue
Yes, that is why many big tech companies have their european hq there.
You’re right, Google released their vision in 2023, here is what it says regarding lifespan:
a reduction of TLS server authentication subscriber certificate maximum validity from 398 days to 90 days. Reducing certificate lifetime encourages automation and the adoption of practices that will drive the ecosystem away from baroque, time-consuming, and error-prone issuance processes. These changes will allow for faster adoption of emerging security capabilities and best practices, and promote the agility required to transition the ecosystem to quantum-resistant algorithms quickly. Decreasing certificate lifetime will also reduce ecosystem reliance on “broken” revocation checking solutions that cannot fail-closed and, in turn, offer incomplete protection. Additionally, shorter-lived certificates will decrease the impact of unexpected Certificate Transparency Log disqualifications.
If you measure from the surrounding area, the Mauna Kea is higher than Mt. Everest.
Sorry, I understood you wrong. You’re right!
Nothing of value was lost when EV certificates disappeared.
even more secure with the 90 days policy.
ssh with an easy to guess root password?