Skip to content
This repository has been archived by the owner on Apr 19, 2024. It is now read-only.

PuTTYTray windows can't be shared in Skype For Business. Normal PuTTY works fine. #260

Closed
ziesemer opened this issue Oct 14, 2016 · 4 comments

Comments

@ziesemer
Copy link

When using Skype for Business, I cannot share a PuTTYTray window / app / program, without sharing the entire screen / display / monitor that it is on. After using "Present" / "Present Programs..." from Skype FB, PuTTYTray simply does not appear in the list of programs that can be shared. This happens whether at the saved sessions dialog, or for a connected session. All of this works fine with the native PuTTY client.

I don't immediately see any differences between the PuTTY and PuTTYTray windows that would explain this. I can operate on each window the same through Process Explorer, for example: Selecting the process by using the window selector, as well as using the "Bring to Front", etc., commands. I am also not running PuTTYTray as an elevated process, which would prevent this.

Windows 10.0.14393. Skype for Business 2016 MSO (16.0.4432.1000) 64-bit.

@cartel0x27
Copy link

Process ACLs were loosened on the upstream putty, perhaps they are too tight on PuttyTray?

@ziesemer
Copy link
Author

Process ACLs were loosened on the upstream putty, perhaps they are too tight on PuttyTray?

That seems to be an understatement, and agreed. Using Process Explorer against 0.67 versions (PuTTY and PuTTYTray ), I can't even view my own process details - running everything together as the same user.

This is fixed in PuTTY 0.68 (based on my testing). It looks like the fix for this is e22120f. See also: http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/win-process-acl-finesse.html

(Looks like my initial report here must have been with PuTTY 0.66 and PuTTYTray 0.67 - my bad.)

Anxiously awaiting the 0.68 rebuild (#264), for this and other concerns. (Using native PuTTY in the meantime.)

@ziesemer
Copy link
Author

ziesemer commented Nov 4, 2017

Requires: #278.

@FauxFaux FauxFaux added this to the release on 0.70 milestone Jul 18, 2018
@FauxFaux
Copy link
Owner

I'm just going to assume this will be fixed by the re-relaese, without testing it. Please feel free to re-open should a re-release happen, and it's still broken.

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants