The article traces mandatory complex password rules to Bill Burr's 2003 NIST guide based on a 1980s paper, reveals how they create predictable patterns, cites xkcd's entropy comparison, and notes Burr's 2017 regret and NIST's updated guidelines, yet many sites still enforce the outdated rules.
This article explains why websites require password resets instead of revealing original passwords, detailing how secure systems use one-way hashing algorithms like bcrypt and Argon2 combined with unique salts to store only irreversible password hashes, making original password recovery mathematically impossible while protecting against database breaches and credential stuffing attacks.
Kaspersky Lab’s analysis of 2.31 billion leaked passwords reveals that 60% can be cracked in under an hour—nearly half in under a minute—thanks to RTX 5090‑level GPU hashing speeds, AI‑driven guessing, and persistent human habits, prompting urgent security reforms.
This guide walks through Linux user management fundamentals—core files, user creation, modification, deletion, login processes, password policies, audit logs, and anti‑brute‑force measures—highlighting common mistakes and practical safeguards to harden server security.
A security analysis reveals that Microsoft Edge keeps all saved passwords in plaintext within process memory, dramatically widening the attack surface, while Microsoft’s terse "by design" response raises serious concerns for both individual users and enterprises, prompting urgent mitigation recommendations.
A 158‑year‑old British transport company was crippled by a ransomware attack after hackers guessed an employee's weak password, leading to full data encryption, massive financial loss, bankruptcy, and highlighting systemic IT security failures.
Google Chrome now offers an automatic password‑change function that detects leaked credentials, generates strong passwords, and updates them with minimal user effort, while websites must adopt specific autocomplete attributes and change‑password URLs to integrate seamlessly with this security enhancement.
This article explains how to improve website password security in PHP by using modern hash functions, adding random salts, employing built‑in password hashing APIs, enforcing strong password policies, scheduling regular password changes, and implementing measures to prevent brute‑force attacks.
This article explains how PHP's password_hash function creates cryptographically strong, salted password hashes, demonstrates its usage with example code, and shows how to verify passwords securely using password_verify, emphasizing best practices for backend security.
Meta was fined €91 million by Ireland’s Data Protection Commission for storing user passwords in plain text, violating multiple GDPR provisions and highlighting the critical need for proper encryption and data‑security measures in large‑scale online services.
The article presents NordPass's annual most‑used password list, highlights the top ten weak passwords in China that can be cracked in seconds, explains why users choose them, and offers four practical recommendations for creating stronger, more secure passwords.
Websites cannot reveal original passwords because they store only salted, one‑way hashes, not the plaintext, making recovery impossible; therefore, when users forget their credentials, the secure approach is to verify identity and issue a password reset rather than expose any stored data.
This article explains how to enhance website password security in PHP by using hash functions, adding salts, employing password_hash and password_verify, enforcing strong password policies, scheduling regular password changes, and implementing measures against brute‑force attacks.
NordPass analyzed a 3 TB dataset from 30 countries to identify the most common 2022 passwords, showing that weak, easily guessable passwords still dominate, cultural trends affect password choices, and providing practical advice for improving online security.
The article argues that traditional password complexity rules and periodic resets are outdated, advocating for longer passwords, the use of password managers and multi‑factor authentication, and limiting login attempts to improve security in modern, always‑connected systems.
This article examines why passwords are often insecure, explains how they should be stored using hash algorithms and salts, outlines common password‑weaknesses and system vulnerabilities, and introduces FIDO/WebAuthn as a modern, password‑less authentication solution.
An investigation reveals how weak credentials like "admin" and "123456" persisted in Ukraine’s military control systems, exposing massive data to low‑skill attackers and highlighting the urgent need for stronger password policies across critical infrastructure.
The article reveals how millions still use weak passwords like "123456", highlights a Ukrainian military system compromised by default credentials, and offers practical guidelines for creating stronger passwords to protect personal and organizational data.
This article explains why password security is critical, describes symmetric and asymmetric encryption methods, details how HTTPS and RSA protect data in transit, and outlines best practices for securely storing passwords using hashing, salting, BCrypt, and PBKDF2.
The article explains why the rare password “ji32k7au4a83” appears in breach data, traces its origin to the Chinese Zhuyin phonetic system, presents statistics on common passwords, and offers expert advice on crafting secure, long, and varied passwords.
The 2020 NordPass survey reveals that simple numeric passwords like "123456" remain the most common weak passwords, highlighting new risky entries and offering practical advice for creating stronger, more secure credentials.
The article examines how a seemingly random string ‘ji32k7au4a83’ appears 141 times in the Have I Been Pwned password database, explains its origin in the Chinese Zhuyin phonetic system, and offers practical guidelines for creating stronger passwords to avoid common security pitfalls.
This article explains why Chinese characters are rarely allowed in passwords—due to historical, technical, and usability reasons—and provides practical tips for creating stronger, more secure passwords using letters, numbers, and symbols.
The article explains how a seemingly random password "ji32k7au4a83" appeared in millions of data breaches because it encodes the Chinese phrase "my password" in Zhuyin, highlights the prevalence of weak passwords like "123456", and offers practical advice for creating stronger, more secure passwords.
The article explains why the seemingly random password “ji32k7au4a83” appears in breach data, traces its origin to the Chinese Zhuyin phonetic system, and provides practical recommendations for creating strong, hard‑to‑guess passwords.
This article explains why transmitting passwords over plain HTTP is unsafe, introduces HTTPS and its TLS encryption process, compares symmetric and asymmetric encryption methods, and recommends secure password storage techniques such as salted hashing and BCrypt to protect against rainbow‑table and brute‑force attacks.
This article explores the prevalence of weak passwords, introduces fundamental concepts of cryptography, explains symmetric encryption algorithms and their key distribution challenges, and demonstrates the Diffie‑Hellman key‑exchange process with a concrete example and a Python implementation of primitive‑root calculation.
A recent NordPass analysis of the 200 most common passwords in 2020 shows why simple strings like "123456" dominate, how millions of accounts are exposed, and offers practical advice on creating stronger, unique passwords to protect against breaches and phishing attacks.
The article describes a puzzling MySQL 5.7 situation where any password works, investigates the cause as the auth_socket authentication plugin, provides exact SQL commands to fix the issue, and explains the plugin's security characteristics and appropriate deployment scenarios.
A NordPass analysis of 275 million passwords uncovered the 2020 top‑200 most used passwords, highlighting why simple strings like “123456” are easily cracked and offering practical advice—including length, complexity, and unique generation techniques—to help users create far stronger, unbreakable passwords.
Storing passwords in plaintext is insecure; instead, use cryptographic hash functions with proper salting, avoid simple encryption like AES, understand rainbow table attacks, and adopt modern password‑hash algorithms such as Argon2, Bcrypt or Scrypt to protect user credentials against modern threats.
This article outlines twelve essential cybersecurity practices for 2019, covering biometric authentication, tiered security policies, risk‑based approaches, regular backups, IoT security, multi‑factor authentication, password management, least‑privilege principles, privileged‑user monitoring, third‑party access control, phishing awareness, and employee training.
This guide explains why strong, unique passwords matter, outlines best‑practice guidelines, and provides step‑by‑step instructions for installing and using the Linux tools cracklib and pwscore to assess password complexity and receive quantitative strength scores.
A Ukrainian journalist revealed that the armed forces' Dnipro system used default passwords like "admin" and "123456", allowing anyone to access critical network devices and potentially map and infiltrate the entire military network, highlighting severe information‑security risks.
In early June, AcFun announced a massive hack that leaked nearly ten million user records, including IDs, nicknames and encrypted passwords, urging users—especially those who haven’t logged in since July 2017 or use weak passwords—to change them immediately, while noting that the data is already being sold on the dark web.
This article explains how passwords should be encrypted during transmission using symmetric and asymmetric methods such as RSA, why HTTPS is essential, how services like GitHub and Baidu handle login security, and best practices for securely storing passwords with hashing, salting, and strong algorithms like BCrypt and PBKDF2.
This article examines common password‑storage techniques, explains why plain‑text, symmetric encryption, and simple hashes are insecure, and demonstrates how modern algorithms like PBKDF2, bcrypt, and scrypt, together with proper salting and iteration, can effectively protect user credentials against large‑scale cracking attacks.
This article explains MD5's fast but insecure hashing, demonstrates its use for file verification and password storage in Node.js, and shows how adding random salts dramatically improves password protection while also introducing MD5 collision concepts.
This article explains the purpose of key‑derivation functions, compares fast and slow hash algorithms, and explores how moving password stretching to the browser can increase attack costs while balancing usability, with practical code examples and deployment considerations.
This article showcases a collection of quirky, poetically inspired passwords used by programmers, explains their hidden meanings, and presents statistical insights into common password habits such as length, character composition, and usage trends among developers.
This article shares practical techniques for generating passwords that are easy to remember but difficult for others to guess, including using initials of poems, personal info combined with app names and random numbers, and custom keyboard patterns, while emphasizing the importance of a consistent rule.
The article critiques common mandatory password complexity rules, explains why they often reduce security and usability, and proposes simpler, more effective approaches such as longer minimum lengths, pattern restrictions, and using strength estimators like zxcvbn, illustrated with Laravel implementation examples.
This article explores the concept of front‑end slow encryption, explaining how deliberately increasing hashing time can hinder password cracking, discussing implementation techniques, performance trade‑offs, salt handling, adaptive strength strategies, and the broader security implications for web applications.
This article explains the concept of front‑end slow encryption, why making password hashing deliberately slower improves resistance to brute‑force attacks, how to implement it with salts and variable work factors, and the trade‑offs in performance, usability, and server resource consumption.
The article explains why storing plaintext passwords is insecure, describes one‑way hashing, the danger of rainbow tables, how salting and strong hash functions protect credentials, warns against multiple hashing, and outlines practical strategies—including HTTPS and server‑side salts—to secure user authentication.
This article examines how MySQL containers run with Docker often expose root passwords in clear text through environment variables, detailing where the plaintext is stored, the security risks involved, and practical steps to mitigate the vulnerability.
This article examines common pitfalls in password storage—from storing plaintext or reversible encryption to basic hashing, salted hashing, and advanced key‑derivation functions—explaining why each approach can be vulnerable and recommending robust methods like PBKDF2, bcrypt, and scrypt.
