Printable View
hello once again...
okay, this post mainly addresses hackers/security experts...
if a visual basic .net program communicates with an online mysql databse, the connection could be traced easily. is there any way to completely make it untraceable, or give a fake trace to tracers?
thanks
*** do you mean by "trace"?
See what server you're connecting to?
Shouldn't matter unless the server is a piece of crap with security hole everywhere.
let me explain....
i do not want my clients to know which server they are connecting to. anyone with even little hacking experience could figure out what connections are coming out of/into a program, i do not want those connections to be trackable. i do not want any user to be able to tell where the program is getting its information...
Why dont you just call a webservice that access the database. That way there will be an extra layer between the db and the client.
That is unpossible and not needed.Quote:
Originally posted by ramezb84
let me explain....
i do not want my clients to know which server they are connecting to. anyone with even little hacking experience could figure out what connections are coming out of/into a program, i do not want those connections to be trackable. i do not want any user to be able to tell where the program is getting its information...
You cannot hide where a connection is going to from a computer if the user knows how to find them. You can use a proxy server and then all they will know is that it's going to Server B but Server B forwrds to Server A.
But I don't see any point in what you want done at all. If the server admin has any bit of knowledge with running a server, it'll be secure.
Hell if my site's bandwidth wasn't done with for the month, I could give you the IP to my site, the MySQL username and password. You wouldn't be able to do jack **** with it because of how the server is setup.
i am not trying to avoid someone hacking into my database, i am trying to avoid someone finding my database server in the first place.. is there no better way around this?
the webservice thing.. if i run the webservice on one server, and the database on the other... the client access the webservice which in turn accesses the database on a remote server... would this completely hide the remote server ip where the database is available?
thanks
Hi,
Do you ever heard about VirtualPC or VMWare.... this is the fake PC (Server) that cheat some of the hacker from the internet. Some of the profession running few fake server (which include the firewall installed) so prevent easy route for hacker to get in.
Try this.... Use VirtualPC do multiple OS redirection which include Linux. This method much immune to hackers.
I hope i am right in this sense.
I think , for online database transactions , they use firewalls plus appling some security policies on every connection to the server . If he overstepped these fences, he'll get into another problem which is unable to login . For me , I wouldn't bother if anyone knew the database server if I made sure it's well secured.
That won't do squat and no good server admin will even use any type of vmware to try and confuse people. I think you're suggesting for the vmware to be on the actual server, but give it it's own ip and forward to itself basically. That is stupid and creates ALOT more security holes in that server than there was before.Quote:
Originally posted by lianwk
Hi,
Do you ever heard about VirtualPC or VMWare.... this is the fake PC (Server) that cheat some of the hacker from the internet. Some of the profession running few fake server (which include the firewall installed) so prevent easy route for hacker to get in.
Try this.... Use VirtualPC do multiple OS redirection which include Linux. This method much immune to hackers.
I hope i am right in this sense.
No matter what, if a connection is coming in or going out of a PC, the users CAN find out what it is sending and where it is going. There is absolutely no way around that. If there was a way to hide the connections, there would be ATLEAST a good 20,000 more viruses, and the RIAA could even install virus without people knowing and then have the virus periodically send out info on what music you have.
Bottom line, if you want a program to connect to a SQL database and you don't want people to know where the server is, you're going to have to use a proxy. If it's all internal, you could use a switch or something to forward a port to that or maybe even a router, but that wouldn't be hiding it very well since it would be as if the switch was the server.
Your best alternative is to make sure the server admin set up the server correctly and make MySQL only accept connections from 127.0.0.1(from itself) and then make a PHP or ASP script in which your program connects to.
okay.. the proxy thing seems to be what i'm looking for... i will look into it then post again here if i can't figure it out...
thanks alot :)