This article reads like an AOL scare from 1995 directed at my grandma.
This article reads like an AOL scare from 1995 directed at my grandma.
Even Bruce Schneier recommends you do that[1]. The idea is that if your machine is a spambot and you don't know it, there are fewer windows of time where your machine can be blasting the Internet with spam. Or if there's some network-based exploit, you're not vulnerable while your device is off.
1. https://www.schneier.com/blog/archives/2004/12/safe_personal...
How old is that article? Sounds like this is from the days back when dial-up was still popular.
I guess there may be some marginal increase in security by turning off your computer like this, but I don't think it's the kind of thing most users should be worried about.
> if your machine is a spambot and you don't know it, there are fewer windows of time where your machine can be blasting the Internet with spam
If your machine is part of a botnet, you're already compromised and turning it off when you're not using it isn't going to fix that. It might marginally help _other_ people getting DDoSed or spammed by your PC, but it won't improve your own security.
> Or if there's some network-based exploit, you're not vulnerable while your device is off
I guess. But unless you become aware of the exploit and take measures to mitigate it before turning your PC on and connecting it to the internet, leaving it off when you're not using it is unlikely to help with this - you'll just be compromised as soon as you turn your PC on. Not to mention that the kind of zero-day that would allow compromising a fully up-to-date PC with nothing more than network access to it is extremely rare.
I'd argue the security benefits of leaving your computer on so it can auto-install security updates while you're away probably outweighs any marginal benefits you might get from turning it off when not using it. (Though either way the difference is extremely minor.)
While currently it would take a state actor to do this eventually this will trickle down into to the hackers.
Also, go look at the submitter's history: https://news.ycombinator.com/submitted?id=vezycash
- - -
But should it be on the front page of Hacker News? Why did vezycash take the effort to share this when it has little value for the HN audience?
The author nevers explain how their domain was stolen, nor do they tell us if the "sting" operation (asking to stop a wire transfer, hardly a sting) was successful. It's a long-winded rant about HostMonster and GoDaddy being shitty. We already knew these things. If the article was just focused criticism on GoDaddy or clear advice on web security, I wouldn't be so hash. Whatever educational benefits there were in article are lost with the writing.
This has got to be on the front page because of some shilling.
Also, HN Guidelines ask you not to suggest people haven't read the article. If you don't like the article, flag it or make a constructive comment (which I think you did) and move on.
In the 2000s, domain hijackings were very common (as tedunangst mentioned):
http://www.metafilter.com/3789/Adobecom-gets-hijacked http://archive.wired.com/politics/law/news/2000/04/35674?cur...
Later on, it became short Twitter accounts:
https://medium.com/@N/how-i-lost-my-50-000-twitter-username-...
https://www.wired.com/2016/06/deray-twitter-hack-2-factor-is...
If your metric is how informative an article is, the above two links about Twitter accounts being hijacked are much more educational than original blogpost.
I think the downvotes are because you're accusing the submitter and the people upvoting this article of shilling based on nothing but circumstantial evidence, not because of your opinion on the quality of the linked article.
People have time to constantly use Twitter/Facebook/YouTube/Reddit/Tumblr/internet forums in general, they can easily post an article on Hacker News once a day.
Some of the other advice in that section is also rather questionable. (E.g. "Your password should not contain “real” words".)