3 ms·
for the longest time we had issues with people pasting passwords in slack to share them within the org. one hackathon later we had a one time secret sharing sl
by avh02 5y ago
for the longest time we had issues with people pasting passwords in slack to share them within the org.
one hackathon later we had a one time secret sharing slash command (which you can only reveal the message once and is then lost/deleted). self-hosted.
it's the thing i'm asked most about if it was OSS after i left the company (by other ex-colleagues looking to have the same thing elsewhere).
- Dwolb 5y agoThat’s a great product by the way. Feels like a Freemium model based on number of unique users could be pretty effective.
- avh02 5y agoyeah, was thinking about rebuilding it as OSS just now. the biggest problem is that a security-minded org is going to want control over the server storing their secret messages (otherwise, you're literally giving away which org you are (slackbots get your org id) and your deepest secrets to a third party) to self-host, i think the slash command setup is more complicated/annoying. but i will look in to it again. edit: and you can't really do E2E encryption with slack as a middleman to your API
- jassra 5y agoIts the haunt of existing premiums that drove me to make this. :) Literally free : )