frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Automated Linux Kernel CVE Detection for the EU CRA (Cyber Resilience Act)

https://hardenedlinux.org/blog/2026-04-06-closing-the-kernel-backport-gap-automated-cve-detection...
1•hardenedlinux•4m ago•0 comments

Migrating RTLS reporting to ClickHouse for 5x faster movement audits

https://navigine.com/blog/navigine-spring-update-2026/
1•SmartDS•5m ago•0 comments

I built as elf healing semantic layer for any AI agent tool

https://github.com/kwstx/engram_translator
2•kwstx•5m ago•1 comments

NASA Shares Photos Shot on iPhone 17 Pro Max During Artemis II Mission

https://www.macrumors.com/2026/04/05/nasa-artemis-ii-photos-shot-on-iphone-17-pro-max/
1•nalekberov•5m ago•0 comments

New Advances Bring the Era of Quantum Computers Closer

https://www.quantamagazine.org/new-advances-bring-the-era-of-quantum-computers-closer-than-ever-2...
1•ibobev•8m ago•0 comments

1SubML: Plan vs. Reality

https://blog.polybdenum.com/2026/04/05/1subml-plan-vs-reality.html
1•ibobev•8m ago•0 comments

Some Subtleties When Parsing 6502 Assembly Language

https://bumbershootsoft.wordpress.com/2026/04/04/some-subtleties-when-parsing-6502-assembly-langu...
1•ibobev•9m ago•0 comments

New library to convert HTML => pdf and dxf (using getBoxQuads for help)

https://github.com/node-projects/layout2vector
1•jogibear9988•10m ago•0 comments

Fooling Go's X.509 Certificate Verification

https://danielmangum.com/posts/fooling-go-x509-certificate-verification/
1•hasheddan•10m ago•0 comments

Ollama and OpenClaw

https://docs.ollama.com/integrations/openclaw
1•zlu•11m ago•0 comments

Former Azure Engineer Alleges Manual Fixes, Firefighting Threaten Reliability

https://windowsnews.ai/article/former-azure-engineer-alleges-manual-fixes-firefighting-culture-th...
1•sylvainkalache•13m ago•0 comments

Ask HN: How do systems (or people) detect when a text is written by an LLM

2•elC0mpa•20m ago•0 comments

ServiceMesh at Scale with William Morgan Creator of Linkerd

https://open.spotify.com/episode/6BbrYeuPftkvJYTZuJfZmm
1•neciudan•24m ago•1 comments

Show HN: Mail Toll – Set a price on your inbox, agents pay USDC to reach you

https://mailtoll.app
1•willgdjones•25m ago•0 comments

Macroeconomic Policy and the Optimal Destruction of Vampires [pdf]

https://irihs.ihs.ac.at/id/eprint/162/1/fo162.pdf
2•AFF87•26m ago•0 comments

Improved the social and emotional system – larkos(neural web)

1•Okerew•29m ago•0 comments

Why Ambiverts Make the Best Leaders

https://www.truity.com/blog/why-ambiverts-make-best-leaders
1•rbanffy•31m ago•0 comments

Linux 7.1 Expected to Begin Removing I486 CPU Suppor

https://www.phoronix.com/news/Linux-7.1-Phasing-Out-i486
2•mariuz•33m ago•0 comments

What if AI just makes us work harder?

https://timharford.com/2026/04/what-if-ai-just-makes-us-work-harder/
5•penguin_booze•38m ago•1 comments

Python: Profiling-Explorer

https://adamj.eu/tech/2026/04/03/python-introducing-profiling-explorer/
1•elashri•38m ago•0 comments

Go 1.25 and 1.26 Compiler Magic – How the Stack Is Eating the Heap

https://programmerscareer.com/go-stack-allocation-optimizations/
3•swq115•38m ago•0 comments

Lichess and Take Take Take Sign Cooperation Agreement

https://lichess.org/@/Lichess/blog/lichess-and-take-take-take-sign-cooperation-agreement/DZS0S0Dy
2•dematz•40m ago•0 comments

Why RAG doesn't work for WhatsApp AI agents and what's the alternative

https://wpp.opero.so/blog/why-rag-fails-for-whatsapp-and-what-we-built-instead
2•juancruzguillen•41m ago•1 comments

Satellite mirror plans could disrupt sleep and ecosystems, scientists say

https://www.theguardian.com/science/2026/apr/05/satellite-mirror-plans-could-disrupt-sleep-and-ec...
1•giuliomagnifico•44m ago•0 comments

Tiny Corp's Exabox

https://twitter.com/__tinygrad__/status/2040944508402360592
7•macleginn•44m ago•0 comments

Upwork Inc. violates its own DMARC and SPF policy

2•tmcdos•45m ago•1 comments

Ice-Out: Retiring IceLen until winter late 2026

https://www.bassfinity.com/blog/ice-out-2026-icelens-seasonal-close
1•jequals5•50m ago•0 comments

SQLite on Git, Part II: Unlocking Zlib's Less Known Feature

https://blog.lysk.tech/sqlite-on-git-part-2/
3•mlysk•50m ago•1 comments

Why Taking over Utilities Won't Deliver Cheap Electricity

https://oilprice.com/Energy/Energy-General/Why-Taking-Over-Utilities-Wont-Deliver-Cheap-Electrici...
1•PaulHoule•51m ago•0 comments

Ansel: Color Controls Finally Correct

https://ansel.photos/en/news/color-controls-finally-correct/
1•aurelienpierre•51m ago•0 comments
Open in hackernews

Are Your Passwords in the Green? (2025)

https://www.hivesystems.com/blog/are-your-passwords-in-the-green
1•kemotep•11mo ago

Comments

kemotep•11mo ago
With NIST finally updating their standards to recommend 15 character password minimums last, I like to use their recommendations and compare them to these charts show how effective such a password would be.

Using E = L x log2(R), where E is entropy, L is number of characters in the password (15), and R is the total number of possible characters used (26 for all lowercase letters), you can get ~70 bits of entropy. Using a password manager like Bitwarden for a 15 character password using the full character set minus the ambiguous characters (65 characters total) leads to ~90 bits of entropy.

Using these charts and figures from the article, a well configured bcrypt setup means even the fastest computer systems still in 2025 cap out at 1 billion hashes per second for offline cracking (without getting into Nation States spending billions on just cracking your passwords, or dedicating all the world’s supercomputers or some other speculations). So to calculate how long it would take with a “realistic” password cracker in 2025, would use this formula:

((((((2^(70-1))/ 1 billion hashes per second)/ 60 seconds)/ 60 minutes)/ 24 hours)/ 365 days) to get ~18,700 years. (Nearly 20 billion years for the Bitwarden generated one)

But without a password filter checking for known bad passwords somewhere like Have I Been Pwned, even a 30 character password that has been leaked is useless. Would be instantly “cracked”. So I personally would have the password policy be:

1. 15 character minimum, no composition rules.

2. All passwords filtered for known bad passwords against HIBP.

3. Accounts protected by MFA.

4. Combination of network controls, best practices security configurations, and alerts and monitoring to help detect and limit/eliminate password guessing attacks, password database dumps.