[yawndex]

Why does the "share" button upload the password to your server in plaintext?

[zamadatix]

The "share which expires after one use" part requires the password either be visible to the server or encoded in the URL (also visible to to the server) unless you also want to share a password/key to access the password or, in which case the site doesn't make sense, or you want to require both folks are online at the same time to make a brokered WebRTC connection and share via that channel.

I think the intent is you have some crap messaging platform like email or SMS without and want to send a one time access link to the password. I'm not really sure how large the intersection of people who care enough about security to want that but not enough to want to avoid a 3rd party server and hoping first access of the link contents is by the intended target is though.

[new_user_final]

https://temp.pw/?item=82282c4798d60cb4#key=idh36ud

I think something like this could work.

The server store encrypted password identified by item id. Browser side decrypt the encrypted password using key in the hash part. The hash part does not reach the server.

[Edd314159]

It has to, how would it deliver the password to the URL’s recipient otherwise?

I suppose to keep it fully stateless you could encode the password in the URL itself somehow, but then that would defeat the purpose of not having the secret hang around in perpetuity.

[bn-usd-mistake]

Encrypt password with a given key, send that to the server. Include the key in the `#fragment` of the URL to Share.