81–90 of 150 posts
Your product looks great. I watched the demo on the home page and I'm impressed.
I'm definitely going to give a try. The developer integration seems awesome.
Congratulations on the release.
Tom here from Doppler. I'm a founding engineer at Doppler and work on most of our security. Feel free to hit me with any security questions about our product, philosophy, etc.
Hey Tom! I see in the security section it says "We secure your data at rest through a mechanism called tokenization, which ensures our systems only store references to your secrets. In the event of a data breach, attackers would only gain access to the references." If this is the case, then where are the secrets stored? How can you view the secrets from the web console if they aren't stored anywhere? Thanks!
[0] https://docs.doppler.com/docs/security-fact-sheet#data-flow-...
I don't write much on Hacker Nees, I'm much of a reader. But... Your product looks great. I watched the demo on the home page and I'm impressed. I'm definitely going to give a try. The developer integration seems awesome. Congratulations on the release.
Earlier quoted context omitted.
Hi, congrats on the launch! Potentially a little off topic, but I'm curious how you came up with the name Doppler. After the audio effect, or the Witcher creature, or something else entirely?
It is a re-use/pivot of a name for a previous project from Brian that didn't take off: ``` Show HN: Doppler – Machine learning marketplace of pretrained models (producthunt.com) - 6 points by bvallelunga on Apr 25, 2018 | 1 comment ``` It's a cool name for sure, but after perusing the founder of this project's blog posts and other web activity, their highly misleading marketing ("you have three options: waste time, d…
https://www.vaultproject.io/docs/vs
``` More importantly, just as we like to present information about Vault and its capabilities in the ways that we prefer, we felt it wasn't appropriate to describe the capabilities of other projects or products in ways other than their own terms. ```
A few months ago a wrote about how I solve this problem (https://www.viadog.com/replacing-environment-variables-aws-s...) and it works nicely for a small team with a small number of projects but this looks like a very nice solution when starting to scale a little bigger.
Good luck going forward!
How does it fair against Vault? Vault is self hosted and open source.
Does everyone in this thread know the founder or something? No one is asking these and they're in my view the absolutely most important questions.
Earlier quoted context omitted.
Hey Tom! I see in the security section it says "We secure your data at rest through a mechanism called tokenization, which ensures our systems only store references to your secrets. In the event of a data breach, attackers would only gain access to the references." If this is the case, then where are the secrets stored? How can you view the secrets from the web console if they aren't stored anywhere? Thanks!
Great question! We tokenize all secrets and then store the tokens in our database. The raw secrets are stored with our tokenization provider, VGS. When you fetch your secrets, either via our dashboard or CLI, we exchange the token for the raw secret value and then relay that value in our response. This ensures that our infrastructure never persists raw secret values. You can find more information about this process i…
You have to give Doppler your secrets which is absolutely crazy. Is there a self hosted version? How does it fair against Vault? Vault is self hosted and open source. Does everyone in this thread know the founder or something? No one is asking these and they're in my view the absolutely most important questions.
However, please stop trying to contrast yourself with these analogies. Owncloud and Nextcloud both have hosted OR on-prem versions
Earlier quoted context omitted.
Great question! We tokenize all secrets and then store the tokens in our database. The raw secrets are stored with our tokenization provider, VGS. When you fetch your secrets, either via our dashboard or CLI, we exchange the token for the raw secret value and then relay that value in our response. This ensures that our infrastructure never persists raw secret values. You can find more information about this process i…
Thanks for the quick response. I think this should really be explicitly stated in the docs, along with a link to VGS. The diagram didn't make it obvious to me that the "security provider" block is actually storing the secrets, rather than just converting them into tokens.