Thanks for your reply but the question still is what can be done about it and what are my options.
You don't expect the server hosting company to admit that they have "weak security", right?
So unless I can find some way to prove to them, exactly where their flaw is, then I can't persuade them to fix a problem which they don't see, exists.
As it stands now, everyone passes the buck to the other party.
The Server company will say it's a flaw in VB and VB will say it's a flaw in the server shared hosting or whatever else and we as the consumers are stuck in the middle unable to show absolute proof of where the precise fault is at.
Are you suggesting to use non-shared hosting as a remedy? That a bit pricey.
You don't expect the server hosting company to admit that they have "weak security", right?
So unless I can find some way to prove to them, exactly where their flaw is, then I can't persuade them to fix a problem which they don't see, exists.
As it stands now, everyone passes the buck to the other party.
The Server company will say it's a flaw in VB and VB will say it's a flaw in the server shared hosting or whatever else and we as the consumers are stuck in the middle unable to show absolute proof of where the precise fault is at.
Are you suggesting to use non-shared hosting as a remedy? That a bit pricey.
Comment