4 ms·
You forgot the part about exposing your finished database to unprotected elasticsearch http endpoint ;) In all seriousness does anyone know why you can even ho
by davidhyde 7y ago
You forgot the part about exposing your finished database to unprotected elasticsearch http endpoint ;)
In all seriousness does anyone know why you can even host an elasticsearch database as http and without credentials? Seems to be the default. What is the use case for this?
- tomc1985 7y agoThe use case is in a local datacenter, with a NAT-ed IP not exposed to the main web
- kchamplewski 7y agoA firewalled IP would be much more appropriate, and NAT is not a firewall or a security mechanism.
- tomc1985 7y agoSame thing, more-or-less. And NAT is effectively a firewall for inbound traffic, even if a lot of people say it isn't.
- kaivi 7y agoTbh I'm still selling that data. For a while I've had reoccurring nightmares that my DB had been stolen and published together with an article on how stupid and incompetent I am.
- prawnsalad 7y agoIf I've understood you right, you break the TOS on other websites to collect users personal info, and then you have nightmares about people taking that data from you? Doesn't that raise ethical concerns in your eyes?
- Havoc 7y ago>You forgot the part about exposing your finished database to unprotected elasticsearch http endpoint ;) I'll cut straight to the chase and post it on hn. This intermediate step of waiting for someone to discover it takes too long