4 ms·
well, everything has a risk. If someone wants to break, he will break it even with ssh tunneling.... The user 'root' was just an example.
by berksi 14y ago
well, everything has a risk. If someone wants to break, he will break it even with ssh tunneling....
The user 'root' was just an example.
- Piskvorrr 14y agoEverything has a risk, but not all risks are equal. You seem to be saying "no point in closing or even locking the door, just leave everything wide open and put up a sign saying 'please do not enter'; it's the same, as everything has a risk." Is the difference in risk clearer now? As for the example, SSH (or most other remote access solutions) has much more secure modes of operations than MySQL (or any other database) - which shouldn't really be surprising. One of these products is a database (where security is just an afterthought), whereas the other is a tool for secure remote access (where security is the main goal; unless you're the type of user who's blindly clicking "yes yes yes agree yes agree sure yes yes," it's very hard to break SSH). If you insist on deploying insecure systems, that's mostly your problem; please don't advise others to do likewise (as you're actively causing harm by this).
- berksi 14y agodude wtf with the security... chill out. the topic wasn't about mysql security.... i will post a topic about ssh tunneling if that makes you happy. :)
- Piskvorrr 14y agoYup, the topic was "let's just open the server directly onto the network, after all, nothing bad could ever happen on the Internet" (For next topic, I'd suggest "someone hacked my server, stole my data and made it a part of a botnet, halp!!1!").