For a start, try hosting something in your own home. A raspberry or an older PC or laptop should be enough.
My first projects were a print server (so I can print via wifi) and a file server. Try to find something that is useful for you.
Only start hosting on the internet when you’ve learned the basics and have more experience.
Maybe because many streaming services have locked their 4k content behind some specific apps and platforms and offer lower resolutions on general desktop PCs.
Generally, we (sadly) see smart monitors come up like smart TVs did ten years ago.
Some noteable features include streaming apps (netflix…) and wireless screen mirroring from phones.
Really? At least 90% of packets I get are deposited without signature.
I think it is necessary to make a difference between delivering cheap stuff and a new iPhone or laptop.
ssh with an easy to guess root password?
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.
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.
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.
Yes, if you do this manually it will work.
I meant certbot with nginx plugin and http-01 challenge.
You’re right, ssl.com offers this, too.
IMO, sticking to manual processes that are error-prone is a waste of money and not a sign of a honest business.
You can trim it even further:
https://www.amazon.com/dp/B0B6HKB3JF/