- 0 Posts
- 8 Comments
bizdelnick@lemmy.mlto
Selfhosted@lemmy.world•How do I avoid becoming one with the botnet?English
1·13 days agoMakin notes is good for sonething very simple. It’s better to automate deployment with salt, ansible or something similar. A bit more effort at first setup, much easier restoration. Self-documented.
bizdelnick@lemmy.mlto
Selfhosted@lemmy.world•How do I avoid becoming one with the botnet?English
2·14 days agoBy default your OS is secure. You only have to think about what you expose and how can it be broken in. Disable SSH password authentication. Don’t run software that is provided by hobbyists who have no enough security expertise (i. e. random github projects with 1 or 2 contributors and any software that recommends install method
curl <something> | sudo bash). Read how to harden the services you run, if it is not described in the documentation — avoid such services. Ensure that services you installed are not running under root. Better use containerized software, but don’t run anything as root even inside containers. Whenever possible, prefer software from your distro official repos because maintainers likely take care about safe setup even if upstream developers don’t. Automate installing security updates at the day they released.What doesn’t help:
- Security through obscurity. Changing SSH port etc. Anyone can scan open ports and find where SSH is listening.
- Antivirus. It is simply unable to detect each of numerous malicious scripts that appears every day. It just eats your system resources.The best it can do is to detect that your host is compromised, but not prevent this. It is not security, just marketing.
- Making different rules for public internet and DMZ. Consider there’s no DMZ. Assume that your host can be accessed by crackers from anywhere.
bizdelnick@lemmy.mlto
Open Source@lemmy.ml•Histomat of F/OSS: We should reclaim LLMs, not reject them
0·23 days agoThere’s no such a word as plagiarism in free licenses nor in copyright laws. One could violate copyrights or patents or not. Copyleft licenses do not forbid what you call plagiarism. If you want to forbid this as well as training LLMs on your code, you need a new type of license. However I’m unsure if such a license could be considered free by FSF or approved by OSI.
bizdelnick@lemmy.mlto
Open Source@lemmy.ml•Histomat of F/OSS: We should reclaim LLMs, not reject them
0·23 days agoOne of the four essential freedoms is the freedom to study the software and modify it. Studying means training your brain on the open source code. Can one use their brain to write proprietary code after they studied some copylefted code?
bizdelnick@lemmy.mlto
Linux@lemmy.ml•Reproducing a Microsoft corporate environment on Linux.
0·2 years agoNo way. You completely trust them or you do not trust them at all. In any OS. That’s how security works.
bizdelnick@lemmy.mlto
Linux@lemmy.ml•Reproducing a Microsoft corporate environment on Linux.
0·2 years agoIf you want to control users, don’t give them admin privileges.
Most of things you enumerated solve windows specific problems and therefore have no analogs in other OSes.
Have you tried NetBSD?