SShortSingh.
Back to feed

Why Password Length Matters More Than Symbols, and How to Generate Strong Ones

0
·4 views

A guide aimed at developers highlights that password length is the most critical factor in security, far outweighing the common practice of adding symbols or uppercase letters. A 16-character lowercase password can take centuries to brute-force, while an 8-character password with symbols can be cracked in hours. Human-chosen passwords are inherently predictable, making cryptographically secure random generators — such as the browser's crypto.getRandomValues() API — the only reliable way to create truly strong credentials. Experts recommend using 16 or more characters combining all four character sets for database passwords, and 32–64 character alphanumeric strings for API keys and tokens. Password reuse is also flagged as a major risk, with the advice that even a strong password becomes weak the moment it is used across multiple accounts.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

How a Silent Databricks Pipeline Burned $2,300 in 11 Days Without a Single Error

A senior engineer deployed a Databricks MERGE pipeline to production after successful testing on a 40 GB sample, unaware the production gold table was 3.8 TB with no Z-ordering or partition pruning on the merge key. The job ran every 30 minutes, completed without errors, and showed a green status in the Workflows UI — yet scanned the entire 3.8 TB table on every execution. Over eleven days, the pipeline quietly accumulated $2,300 in compute costs against an expected spend of roughly $40, going unnoticed until a monthly DBU report was reviewed. The incident highlights a broader challenge in production data engineering, where pipelines can pass every technical check while simultaneously inflating costs, silently dropping records, or producing subtly incorrect results. Unlike traditional software failures, data pipeline issues rarely trigger loud alerts, meaning engineers must proactively monitor cost, data quality, and latency rather than relying on exit codes alone.

0
ProgrammingDEV Community ·

38 Months of LangChain Commits Reveal Dramatic Slowdowns in Builds and Releases

A data-driven analysis of LangChain's entire git history from January 2023 to March 2026 tracked structural changes across 38 months of commits without relying on external benchmarks. The repository's average CI build time ballooned from a baseline of 9.5 seconds to roughly 55 minutes — 889 times its own norm — and remained elevated at the final measurement. Release cadence, once as frequent as every 30 minutes, slowed to once every six days at its worst, representing a 220-fold deviation from the historical average before eventually recovering. Median commit size also surged, with some commits touching over 130 files compared to a typical count of two, raising concerns about the practical limits of code review at that scale. The analysis notes these signals — build times, release frequency, and commit size — moved in correlation with one another, suggesting interconnected rather than isolated causes.

0
ProgrammingDEV Community ·

OpenAI Codex App Server Lets Developers Control AI Agents via JSON-RPC

OpenAI's Codex App Server is a tool that allows developers to control Codex AI agents programmatically using JSON-RPC, rather than through the standard command-line interface. The server is launched with a single command and listens on standard input, accepting JSONL-formatted requests. Interactions are structured around two core concepts: Threads, which represent full sessions, and Turns, which are individual user-agent exchanges within a session. Developers can use this interface to build custom graphical interfaces, task queues, or orchestration layers on top of Codex. Full protocol specifications are available in the official README on OpenAI's GitHub repository.

0
ProgrammingDEV Community ·

Ace Data Cloud API Enables Image Generation and Editing via Single Endpoint

The Ace Data Cloud Nano Banana Images API allows developers to build image generation and editing workflows through a single POST endpoint at api.acedata.cloud. The API supports two actions — generating images from text prompts and editing existing images — using the same request structure and response format. Developers can choose from several models, request up to four images per call, and optionally provide a callback URL for asynchronous notifications. A successful API response returns a task ID, trace ID, and a data array containing image URLs, which can be persisted in a production backend. The guide also demonstrates practical integration using cURL and a Python wrapper to help developers move from experimentation to application-ready code.