INindigodaddy·Aug 7, 2025
In Password Pusher: Share secrets securely with self-deleting links and audit logspglombardo
PasswordPusher
Ruby2021–2025
pglombardo / PasswordPusher
PasswordPusher
🔐 Securely share sensitive information with automatic expiration & deletion after a set number of views or duration. Track who, what and when with full audit logs.
5Distinct people
8Mentions
0Explicit recommenders
3.2KGitHub stars
What to know before exploring
What it is
🔐 Securely share sensitive information with automatic expiration & deletion after a set number of views or duration. Track who, what and when with full audit logs.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year8 dated mentions
Observed mentions: 2021-03-12 13:02:42 UTC to 2025-08-07 16:10:09 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 3 | 2 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 3 | 0 | 3 |
What Hacker News says
8 sourcesThe best tool I've found for password dissemination (you can create with it too, or not) is Password Pusher
https://github.com/pglombardo/PasswordPusher
East to deploy, and just works, nice set of sane features and defaults.
In Show HN: Stasher – Burn-after-read secrets from the CLI, no server, no trustThis is pretty light on features and details.
When the use case comes up, I like to use https://github.com/pglombardo/PasswordPusher (online version here https://pwpush.com/). Which has generation, customizable # of visits, and a handful of other features.
In Show HN: Temp.pwPassword Pusher: Securely share sensitive information with automatic expiration
1 points · Open discussionPassword Pusher: Securely share sensitive information
3 points · Open discussionOther than the popular password managers mentioned you can try Password Pusher [0]. It's open source, can be self-hosted, and has options like expire link after n loads or days.
[0] https://github.com/pglombardo/PasswordPusher
In Ask HN: How to store and share passwords in a company?(1) A tool like for example https://github.com/pglombardo/PasswordPusher self-hosted offers a way for the user to detect, whether their password has been seen before.
(2) Are you missing the point? "That is how it usually works." -- So why then send a password to an e-mail inbox, like I said a location often controlled by third party and often one with no good record of respecting privacy, if you can completely avoid that?
(3) OK, seems like we did not learn about consent. Why don't you ask your users, whether they are OK with it first, instead of assuming and basing on what is legally possible? Is ethics something too far out of reach?
Lastly a word about what you call security: Your so called security is observed often enough to result in inaccessible accounts. "Extra strict" usually means something along the lines of "oh, now I am goin
Read the rest
g to require your phone number, to send you a message on a second channel to make sure" or "solve these captchas for this untrustworthy third party provider and I will trust their word about you having solved it correctly" (again being tracked of course ...) or similar things. Again circumventing consent, because now it becomes an extortion, extracting more personal data, so that the user can access their account. Your so called security makes for a real shitty user experience and punishes the user for ever switchting their browser.
So what does your "extra strict" mode entail? How are you going to be "extra strict", without any extortion? Are you implementing your own captachas by any chance? Or something similar?
Might be related:
https://github.com/pglombardo/PasswordPusher/
Password Pusher - Open source secure password transfer
Review by Crosstalk Solutions here:
https://www.youtube.com/watch?v=0mpBLRaHtQo
In Bitwarden Send - A trusted way to securely share information with anyone