Mailinglist Archive: opensuse-bugs (7520 mails)
| < Previous | Next > |
[Bug 390478] VNC - persistent session is not possible - "wait = yes" is not working
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Wed, 13 Aug 2008 10:17:21 -0600 (MDT)
- Message-id: <20080813161721.B3B64CC7DD@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=390478
User max@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=390478#c6
Reinhard Max <max@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #6 from Reinhard Max <max@xxxxxxxxxx> 2008-08-13 10:17:21 MDT ---
10.3 and 11.0 use entirely different implementations for Xvnc. The one in 10.3
contains code to make it work with wait=yes, the one in 11.0 does not.
I think supporting wait=yes would defeat the purpose of the -inetd switch to
allow an arbitrary number of on-the-fly generated one-shot vnc sessions.
It would even be a security risk, because vnc sessions created through xinetd
are not password protected. A user who disconnects from such a session without
explicitly locking it at the X level would leave it open for an attacker.
You can use the vncserver script from the tightvnc package or call Xvnc
directly to start persistent vnc sessions that are independent of xinetd.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
User max@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=390478#c6
Reinhard Max <max@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #6 from Reinhard Max <max@xxxxxxxxxx> 2008-08-13 10:17:21 MDT ---
10.3 and 11.0 use entirely different implementations for Xvnc. The one in 10.3
contains code to make it work with wait=yes, the one in 11.0 does not.
I think supporting wait=yes would defeat the purpose of the -inetd switch to
allow an arbitrary number of on-the-fly generated one-shot vnc sessions.
It would even be a security risk, because vnc sessions created through xinetd
are not password protected. A user who disconnects from such a session without
explicitly locking it at the X level would leave it open for an attacker.
You can use the vncserver script from the tightvnc package or call Xvnc
directly to start persistent vnc sessions that are independent of xinetd.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |