TeamViewer's website claims the software has more than 15 million installations in 50 countries. Still, when Nash learned that TeamViewer does monitor for incoming web requests, he said it made him wonder: "What else aren't they telling us?" ![]() "They're sitting in the middle and they're in a position to snoop on all my traffic," he said, adding that he thinks that scenario is unlikely. Nash was able to get Apache up and running again by killing TeamViewer processes on the server, but by then, the client "had quite a bit of irate support requests stacked up."Īlso concerning, said Nash, is TeamViewer's lack of disclosure that its software is receiving incoming traffic sent to machines that run the software. "At that point, basically the webserver is hosed because if Apache tries to start up again, it sees someone else on port 80 and it falls over and dies, which is kind of antisocial behavior," Nash, who is the principal at Toronto-based Nash Networks, told The Register. It turns out the program had opened up its own webserver on the client's machine as soon as Apache went down and in the process made it impossible for the client, a large provider of business software, to restart its proper website. Equally vexing, people who tried to visit the client's website during the 10-hour outage received a message advertising TeamViewer, a maker of widely used software for remotely managing PCs and servers.Īfter 90 minutes of troubleshooting, Nash traced the problem to TeamViewer, which he used to remotely administer the client's servers. On Thursday morning, IT consultant Paul Nash received an urgent call from a client whose Apache webserver had crashed the previous night and inexplicably wouldn't restart.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |