4 ms·
Usually I access databases in my VMs by ssh tunneling. I have no databse server software on my computer. I thought most people work like that.
by spdionis 10y ago
Usually I access databases in my VMs by ssh tunneling. I have no databse server software on my computer. I thought most people work like that.
- cmdrfred 10y agoMost skilled developers probably. The rest can't figure out why the computer next to theirs can't connect to the test database and after googling a stackoverflow anwser have it listen on 0.0.0.0 forever.
- jlgaddis 10y agoIndeed. Turn off SELinux and disable the firewall too! And just leave the password for the MySQL root user blank since it's too much trouble keeping track of them.
- lugg 10y agoI am guilty of this. The real question is will I ever change this habbit? I see percentage of us here locking things down. The rest, and the rest of the developers out there likely won't. This needs to be fixed at the browser level I don't see it being solved any other way that would have the net benefit of having it fixed in the browser. Simply pinning public and local and not allowing local rebinding should have most of the issues resolved.
- apendleton 10y agoTunneling still binds a localhost port to your database, so it'd still be vulnerable to this attack even though it's running a container or VM.
- teilo 10y agoNo, it doesn't. If you are running Vagrant in a bridging config, it has it's own separate IP on the network. If you are running it as a private network, it has it's own IP on a private subnet isolated to the host machine. You have to explicitly do port forwarding to make it work as you describe. EDIT: I'm not thinking straight. Please ignore me.