tdesktop icon indicating copy to clipboard operation
tdesktop copied to clipboard

Published 20 hours ago • verified publisher icon telegramdesktop

Webcam activates without user-confirmation

Open Niko-O opened this issue 3 years ago • 5 comments

Steps to reproduce

  1. Take off your clothes.
  2. No, seriously, take off your clothes.
  3. Ask a friend to help you with a computer problem by remote-desktoping to your computer.
  4. Get an unexpected video-call from someone.
  5. Telegram automatically activates your webcam and shows the preview on your screen.
  6. Your friend compliments you on your form.

The characters and events depicted in this motion picture are entirely fictitious. Any similarity to names or incidents is entirely coincidental.

Expected behaviour

When telegram receives a (video) call, it should keep the webcam disabled. I should get the option to enable the webcam and send my video feed to the caller IFF I choose to do so. The webcam should NEVER be activated unless I manually click the button to activate it.

Actual behaviour

Telegram automatically activates your webcam and shows the preview on your screen. This happens without any confirmation from the user. This means that unless you disable the webcam in the device manager or stick a post-it on its lens, you are always at the risk of a screen-share becoming a webcam-share. This is a very big privacy problem!

Configuration

Operating system: Windows 10

Version of Telegram Desktop: 2.9.2

Used theme: "Classic" with a custom background image.

Niko-O avatar Aug 17 '21 21:08 Niko-O

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

stale[bot] avatar Feb 17 '22 05:02 stale[bot]

slaps stale bot

Niko-O avatar Feb 17 '22 16:02 Niko-O

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Sep 05 '22 02:09 github-actions[bot]

grafik

Niko-O avatar Sep 05 '22 05:09 Niko-O

So, just to be clear: This problem still exists!

Niko-O avatar Sep 05 '22 09:09 Niko-O

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Mar 05 '23 02:03 github-actions[bot]

grafik

How is this still not fixed? It's been over a year!

Niko-O avatar Mar 05 '23 19:03 Niko-O

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Sep 03 '23 01:09 github-actions[bot]

grafik

Niko-O avatar Sep 08 '23 12:09 Niko-O

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Mar 08 '24 01:03 github-actions[bot]

grafik

Niko-O avatar Mar 08 '24 13:03 Niko-O