So the problem seems to be with TW and the display drivers on Computer1. However, when connecting from Computer2 to Computer1, it works. When connecting from Computer1 to Computer2, it doesn't work (as described above). I've installed and reinstalled the TW monitor drivers on both the local and the remote computer, but it doesn't even seem to ATTEMPT to black the remote screen. Since I'm trying the free version of TW before buying, there also is absolutey no help to get from the TW team. You can uninstall TeamViewer 12 from your computer by using the Add/Remove Program feature in the Windows Control Panel. I tried enabling the "Enable black screen option in the settings on the teamviewer "server", but when I did that the client couldn't even connect - it got stuck on "Initializing display parameters" forever. But the remote screen simply doesn't go blank. This is not what we were promised when we were purchasing the product.
The same will be probably valid for version 13, which is coming.
My problem is that "Show black screen" option when connecting to a client doesn't work. We are pushed to upgrade to version 12 now in order to be able to use their product although the app was presented as something, which we can use virtually forever without additional payments. While in most cases an attacker requires an existing session on a system, if the registry/configuration keys were stored off of the machine (such as in a file share or online), an attacker could then decrypt the required password to login to the system.I've been looking for a solution to this, but I cannot seem to find anyone who has solved it (or even have the exact same problem). Description of windows startup items: TeamViewer 12, TeamViewerService.exe. The latest version still uses the same key for OptionPasswordAES but appears to have changed how the Unattended Access password is stored. With versions before v9.x, this allowed for attackers to decrypt the Unattended Access password to the system (which allows for remote login to the system as well as headless file browsing). If an attacker were to know this key, they could decrypt protect information stored in the registry or configuration files of TeamViewer. It used a shared AES key for all installations since at least as far back as v8, and used it for at least OptionsPasswordAES in the current version of the product. TeamViewer Desktop through allows a bypass of remote-login access control because the same key is used for different customers' installations.
0 kommentar(er)
