Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TeamViewer automatically opening after install #212

Open
opus-nbonenberger opened this issue Jan 17, 2022 · 2 comments
Open

TeamViewer automatically opening after install #212

opus-nbonenberger opened this issue Jan 17, 2022 · 2 comments

Comments

@opus-nbonenberger
Copy link

I don't know why, but every time a client installs a new TeamViewer package, the app is opened afterwards. Is there a way to change that behaviour? Our employees are wondering whats happening when the app opens and suspect some kind of malicious remote control operation....

@homebysix
Copy link
Member

Hi @opus-nbo - It looks like that's included in TeamViewer's installer process. I used Suspicious Package to search for open and found this line that looks relevant in a script in the LauncherFull component package.

image

Sometimes vendors build in logic that can be taken advantage of to prevent user-facing app launches. It would take some digging to determine whether such logic exists here.

TeamVIewer appears to have some documentation available for using "silent" install mode, but I'm not sure whether that omits the app launch or not. Might be worth testing.

@ellisdickinson46
Copy link
Contributor

Current Versions

There is logic built into the installer for this functionality. You have to create a file at a particular location that is referenced during the functions section, called by the postinstall script.

In there, under the restartService() function there is a check to see if /tmp/tvonlystartservice exists, if it does the installer will not open the application post-installation.

Simply, create the file before the installer is called; not sure if the contents of the path matter but "1" seems to work fine.
echo "1" > /tmp/tvonlystartservice

Legacy

For clients installing older versions of TeamViewer, this path used to be /tmp/tvPath. This path would have to contain the correct path for client installation as the variable was referenced elsewhere within the installation scripts.
echo "/Applications" > /tmp/tvPath

Some documentation for this behaviour can be found here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants