Moonglade

Modern Markdown blogging with AI-powered localization and search.

Tag: Security


Open-ended question: Which is more secure, Windows or Linux?

This article provides an in-depth comparison of the security strategies of Windows and Linux in typical end-user scenarios. By default, Windows employs technologies such as BitLocker full-disk encryption, TPM hardware trust, Secure Boot, VBS (Virtualization-Based Security), and Windows Hello biometric authentication. These features create a closed-loop defense mechanism spanning from hardware to software, significantly reducing the risks of physical intrusion and malware attacks. For ordinary users, this results in an exceptionally high level of security. In contrast, while Linux offers mechanisms such as LUKS2 encryption, Secure Boot, and sudo permission control, and its open-source nature allows for deep customization to minimize the attack surface, its security features are often not enabled by default. Furthermore, leveraging these features heavily relies on the user’s technical proficiency for manual configuration and maintenance, posing a higher operational barrier and potential risks. The article points out that security is not an absolute concept but a relative one, based on specific use cases, potential threats, and the user’s technical capabilities. For ordinary users seeking out-of-the-box convenience and high security, Windows offers a clear advantage. Conversely, for developers or server environments that require professional expertise, high flexibility for customization, and code transparency, Linux provides a higher security ceiling and greater flexibility. Therefore, which system is more secure depends on the user’s specific needs and usage patterns.

Views 632
BitLocker Operating Systems Security Use Cases User Experience VBS





Is hashing passwords on the frontend a good approach?

This article uses a riddle about password hashing to reveal the limitations of front-end hashing in security mechanisms. It points out that if data is only hashed on the front end before transmission, the server effectively degrades to plain-text comparison. This allows operations personnel to use the hash value directly to call the API and log in, thereby negating the purpose of security protections. The author reviews the historical practice of early Tencent QQ, which used two-pass hashing to prevent man-in-the-middle attacks, and explains why this scheme failed due to vulnerability to replay attacks. True defense against man-in-the-middle attacks relies on TLS encryption. Drawing from personal experience, the author describes how, during the era of rampant ARP spoofing, plaintext protocols like email were easily attacked, while modern TLS handshake mechanisms have significantly improved communication security. Finally, the article emphasizes that technical measures are not a panacea. Social engineering attacks, such as browser plugin abuse and phishing sites, remain a significant threat. Enhancing users' security awareness and basic judgment skills is the fundamental solution.

Views 626
Hash Password Security hashing algorithm manual in the middle attack password security