News for hackers. Stuff that matters.

stanguc

Show HN: MyPDFBoy – Free PDF redaction that deletes the data

https://mypdfboy.com/

Most free PDF "redaction" tools just draw a black box on top. The text is still there -- select all, paste, done. MyPDFBoy actually removes content from the PDF content stream. What's gone is gone.Upload a PDF, draw rectangles over what you want removed, download. Free, no account, 5 languages including Arabic RTL.https://mypdfboy.comBuilt with React + FastAPI + PyMuPDF. Would love feedback on...

( Read More... | no comments | 2 points | on HN )
easily "bypassable", trust me :)
Re: on Friday February 06, 2026 @03:11PM (#46917548)

  I scanned all 58 official AWS Terraform modules. Here's what I found.

  terraform-aws-modules is the gold standard. 30k+ GitHub stars on the VPC module alone. Used by thousands of teams in production.

  I pointed MonPhare at the entire org:

    monphare scan --github terraform-aws-modules

    45 seconds later: 58 repos scanned, 2,315 files parsed, 3 errors, 692 warnings.


  Even the best-maintained modules in the ecosystem have constraint hygiene gaps -- missing pins, no upper bounds, unbounded providers that welcome breaking changes on any terraform init.

  Now imagine your own infrastructure. Dozens of repos, hundreds of modules, multiple teams pushing changes. Who's checking that a provider upgrade won't break prod on Monday morning?

  That's what MonPhare does.

  One command to audit version constraints across your entire Terraform/OpenTofu state:

  - Scan a local directory, a remote repo, or an entire GitHub/GitLab/Azure DevOps/Bitbucket org
  - Detect missing constraints, unbounded versions, wildcard pins, deprecated modules, and cross-repo conflicts
  - Generate dependency graphs in DOT, Mermaid, or JSON -- see exactly what depends on what
  - Output as formatted CLI tables, machine-readable JSON, or self-contained HTML reports
  - Drop --strict into your CI pipeline -- warnings become blocking errors, nothing slips through
  - Define policies in monphare.yaml -- deprecation lists, required upper bounds, exclusion patterns -- and enforce them across every
  repo

  Written in Rust. Parallel scanning. Shallow clones with local caching. An entire GitHub org in under a minute.

  Open source: https://github.com/tanguc/monphare

What's your workflow to pass cloud secrets/config metadata to apps safely?

I’ve been doing DevOps for about 9 years, and I keep seeing the same mess repeat itself:- Terraform or Pulumi outputs → Vault/KMS → CI replaces values in YAML → K8s secrets operator injects env vars → app starts → DATABASE_PASSWORD typo, chaos ensues.- Copy-pasted creds from Slack or Teams.- Secrets/configs left in plaintext files or repos.- Password managers with outdated entries that no one...

( Read More... | no comments | on HN )

Show HN: Oneseal – Secrets, configs, and platform outputs as code

https://github.com/oneseal-io/oneseal

I kept hitting the same problem: teams pass secrets/configs/IDs via .env files, Slack, or CI glue; Terraform (or Pulumi) knows the truth, but apps don’t. Things drift.I built Oneseal: a small CLI that turns platform outputs (Terraform state, etc.) into a typed, versioned SDK you can install and import. The goal is to make consumption predictable and diffable, not to replace your vault.What it...

( Read More... | no comments | 3 points | on HN )