OT: Dealing with a hosting company with it's head up it's rear end

Olivier Olivier.Nicole at cs.ait.ac.th
Fri Aug 14 08:19:11 UTC 2020

> Tried and their answer is if we insist on breaking the contract then they
> will terminate it and ask for additional penalties under the breach
> clause.

Considering that the hosting company is reponsible to break things, they
are he one to pay the penalties... But I take it you are not a lawyer,
neither I am.

> There website claims they are in full compliance with HIPAA (the relevant
> regulation in the US) and use it as a marketing point.

I am wondering if their idiocy with HTTPS is and if that would not be
worth reporting them to the right agencies.

> The client based on a) recommendations from our old hosting provider who
> decided to go out of business due to the owner retiring, b) the maker of
> the devices we have connectected to the system (actually the manufacturer
> is another fine example of head up the ass... stuff like not even knowing
> what "concurrency" was when asked a question about how the devices interact
> with the vendor provided front-end/DB [which sucks and thus our ground up
> rewrite of it] and when we pressed the matter where told "don't go down
> that rabbit hole", this confirms something another poster said that any
> software company that uses MSSQL get weird quickly -- the version of the
> devices we have current use MySQL but the next generation only "support"
> MSSQL since it is "better" than MySQL) and 3) by the fact that they were a
> publicly traded (NY Stock Exchange)

You had no saying in the choice of the hosting company, so you can
report to your client that given the circunstances, you cannot help and
that your client should deal with the matter. There is a limit to what
we can do technically.

You mentioned that piort 25 is open, you could modify some SSH client
and server to start the connection like and SMTP protocol, launch
STARTLS then so some SSH inside. If the 1st packed is an EHLO and
everything after is encrypted, they cannot see what is inside.


More information about the freebsd-questions mailing list