RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
I set "Approve All Connections" to "ON" in Screen Sharing because I thought it meant that all connections would be allowed automatically. I also set up password protection so only I could connect remotely. However, when I tried to get back to my screen, I couldn't; I was locked out. The thing is, it's the other way around: "ON" means that all connection attempts must be manually approved by the local user. Go figure.

Would you please consider rewording the description of the switch?

Version-Release number of selected component (if applicable):
vino-3.8.1-7.el7

FWIW, in vino-preferences, before it was deprecated, there was a nice checkbox:

"You must confirm each access to this machine"

Unless I'm misunderstanding something, the UI would have to be changed in control-center.

Created attachment 857428 [details]
mockup

I agree that the options need to be clearer here. Part of the issue is the wording of the label. The other part is that the two check boxes are ambiguous - it isn't spelled out what will happen when neither of them are checked.

I've developed the attached mockup in consultation with the vino and control center maintainers. It makes the different options clear, and also deliberately prevents people from leaving their systems open (this is still possible for those who have expertise; we just won't show it in the UI).

Note that a password will need to be generated when "require a password" is selected.

Looks great!

too late for 7.0

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2157.html