Enable BuildGlxExt (to avoid errors 'Xlib: extension "GLX" missing on display ":1.0"')
|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
 |
Enable BuildGlxExt (to avoid errors 'Xlib: extension "GLX" missing on display ":1.0"')
by Heiko Meyers
::
Rate this Message:
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___________________________________________________________ TightVNC mailing list, VNC-Tight-list@... To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list |
|
|
|
How to interpret the WinVNC.log file
by Edward Jubenville-3
::
Rate this Message:
I am using TightVNC
Server 1.3.10.
I have the "Log
information to WinVNC.log" option selected, but not "Log detailed debugging
information".
The server VNC icon
in the system tray doesn't seem to provide any means to look at a list of
current connections. Is there an active connection list to be
seen?
How can I tell when
an intruder makes it through the password prompt?
Are all
non-timestamped lines associated with the same event, i.e., associated with the
preceding timestamp?
Following is a
contiguous chunk of messages from my log file.
vncSockConnect.cpp: accepted connection from 145.236.32.141 vncClient.cpp: client connected : 145.236.32.141 (id 1) Thu Nov 05 10:24:59 2009
vncClient.cpp: non-standard protocol version 3.5, using 3.3 instead Thu Nov 05 10:25:01 2009 vncClient.cpp: Client connection rejected Thu Nov 05 10:25:03 2009
vncSockConnect.cpp: accepted connection from 145.236.32.141 vncClient.cpp: client connected : 145.236.32.141 (id 1) vncClient.cpp: non-standard protocol version 3.5, using 3.3 instead Thu Nov 05 10:25:04 2009 vncClient.cpp: Client connection rejected Thu Nov 05 11:46:00 2009 vncSockConnect.cpp: accepted connection from 78.8.29.249 vncClient.cpp: client connected : 78.8.29.249 (id 1) vncSockConnect.cpp: accepted connection from 78.8.29.249 vncClient.cpp: client connected : 78.8.29.249 (id 1) Thu Nov 05 11:46:09 2009 vncClient.cpp: incorrect security type requested Thu Nov 05 11:46:15 2009 vncSockConnect.cpp: accepted connection from 78.8.29.249 vncClient.cpp: client connected : 78.8.29.249 (id 1) vncClient.cpp: non-standard protocol version 3.5, using 3.3 instead Thu Nov 05 11:46:21 2009 vncClient.cpp: performing VNC authentication vncClient.cpp: authentication failed Thu Nov 05 11:46:27 2009 vncSockConnect.cpp: accepted connection from 78.8.29.249 vncClient.cpp: client connected : 78.8.29.249 (id 1) vncClient.cpp: non-standard protocol version 3.5, using 3.3 instead Thu Nov 05 11:46:33 2009 vncClient.cpp: performing VNC authentication vncClient.cpp: authentication failed Thu Nov 05 11:46:39 2009 vncSockConnect.cpp: accepted connection from 78.8.29.249 vncClient.cpp: client connected : 78.8.29.249 (id 1) vncClient.cpp: non-standard protocol version 3.5, using 3.3 instead Thu Nov 05 11:46:45 2009 vncClient.cpp: performing VNC authentication vncClient.cpp: authentication failed Thu Nov 05 11:46:51 2009 vncSockConnect.cpp: accepted connection from 78.8.29.249 vncClient.cpp: client connected : 78.8.29.249 (id 1) vncClient.cpp: non-standard protocol version 3.5, using 3.3 instead Thu Nov 05 11:46:57 2009 vncClient.cpp: performing VNC authentication Thu Nov 05 11:46:58 2009 vncClient.cpp: authentication failed Thu Nov 05 11:47:03 2009 vncSockConnect.cpp: accepted connection from 78.8.29.249 vncClient.cpp: client connected : 78.8.29.249 (id 1) vncClient.cpp: non-standard protocol version 3.5, using 3.3 instead vncClient.cpp: Client connection rejected Thu Nov 05 11:47:09 2009 vncSockConnect.cpp: accepted connection from 78.8.29.249 vncClient.cpp: client connected : 78.8.29.249 (id 1) vncClient.cpp: non-standard protocol version 3.5, using 3.3 instead vncClient.cpp: Client connection rejected In the above
log, there is no clear indication that a connection was fully successful in
gaining access to my desktop, but I'm not sure if I would always see such an
indication. When I myself connect to my desktop, I see this in
the log: Thu Nov 05 12:48:04
2009
WallpaperUtils.cpp: KillActiveDesktop vncDesktop.cpp: not activating video driver interface vncBuffer.cpp: unknown encoder requested Does
the absence of this information following an intruder attempt mean the
intrusion failed?
I'm not a
contributor to the TightVNC source code, but would it be simple for somebody to
add a positive message such as "Desktop access granted" to the log
file?
Thanks,
Ed
J
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___________________________________________________________ TightVNC mailing list, VNC-Tight-list@... To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list |
|
|
|
Re: Enable BuildGlxExt (to avoid errors 'Xlib: extension "GLX" missing on display ":1.0"')
by Constantin Kaplinsky
::
Rate this Message:
Hello Heiko,
>>>>> Heiko Meyers wrote: > How can I solve the problem? > Is the single change "#define BuildGlxExt YES" in vnc.def the correct approach? I don't think so. Probably Xvnc from the TightVNC distribution does not include GLX support at all. I think it might be a good idea to search for solution on Google: http://www.google.ru/search?q=Xvnc+GLX -- With Best Wishes, Constantin ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___________________________________________________________ TightVNC mailing list, VNC-Tight-list@... To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list |
|
|
|
Re: How to interpret the WinVNC.log file
by Constantin Kaplinsky
::
Rate this Message:
Hello Edward,
>>>>> Edward Jubenville wrote: > Thu Nov 05 11:47:09 2009 > vncSockConnect.cpp: accepted connection from 78.8.29.249 > vncClient.cpp: client connected : 78.8.29.249 (id 1) > vncClient.cpp: non-standard protocol version 3.5, using 3.3 instead > vncClient.cpp: Client connection rejected > > In the above log, there is no clear indication that a connection was fully > successful in gaining access to my desktop, but I'm not sure if I would > always see such an indication. When I myself connect to my desktop, I see > this in the log: > > Thu Nov 05 12:48:04 2009 > WallpaperUtils.cpp: KillActiveDesktop > vncDesktop.cpp: not activating video driver interface > vncBuffer.cpp: unknown encoder requested > > Does the absence of this information following an intruder attempt mean the > intrusion failed? This information is written on connecting the first client. If then the second client connects, there will be no lines about KillActiveDesktop and video driver. So, in the most general case, these lines do not prove anything. However, if nobody else was using TightVNC at that moment, and the configuration did not change (e.g. "Remove Wallpaper" setting was always on), then their absence is enough information to tell that there was no intrusion. A more reliable way might be to find all the error messages corresponding to "accepted connection". Unfortunately, successful authentication is reported only on higher log levels. I think this behavior is wrong and should be fixed. > I'm not a contributor to the TightVNC source code, but would it be simple > for somebody to add a positive message such as "Desktop access granted" to > the log file? We'll fix this in future versions. Thank you. -- With Best Wishes, Constantin ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___________________________________________________________ TightVNC mailing list, VNC-Tight-list@... To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list |
|
|
|
|
|
|
|
Re: Enable BuildGlxExt (to avoid errors 'Xlib: extension "GLX" missing on display ":1.0"')
by James Weatherall-2
::
Rate this Message:
Heiko,
The VNC Enterprise Edition server supports GLX out-of-the-box, using the Mesa software renderer, so if you're not averse to pay-for software then you might try that. For VNC Free Edition & TightVNC servers, probably the easiest way to get GLX support is to use VirtualGL. It does require that apps access GLX via libGL, and that the console graphics card supports "pbuffers" (off-screen render buffers, essentially), but it's reasonably straightforward to set up. HTH, -- Wez @ RealVNC Ltd Constantin Kaplinsky wrote: > Hello Heiko, > >>>>>> Heiko Meyers wrote: > >> How can I solve the problem? >> Is the single change "#define BuildGlxExt YES" in vnc.def the correct approach? > > I don't think so. Probably Xvnc from the TightVNC distribution does not > include GLX support at all. > > I think it might be a good idea to search for solution on Google: > > http://www.google.ru/search?q=Xvnc+GLX > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___________________________________________________________ TightVNC mailing list, VNC-Tight-list@... To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list |
|
|
|
Re: Enable BuildGlxExt (to avoid errors 'Xlib: extension "GLX" missing on display ":1.0"')
by Heiko Meyers
::
Rate this Message:
--- James Weatherall <james.weatherall@...> schrieb am Mo, 9.11.2009: > Von: James Weatherall <james.weatherall@...> > Betreff: Re: Enable BuildGlxExt (to avoid errors 'Xlib: extension "GLX" missing on display ":1.0"') > An: "Constantin Kaplinsky" <const@...> > CC: "Heiko Meyers" <heikomeyers@...>, vnc-tight-list@... > Datum: Montag, 9. November 2009, 12:41 > Heiko, > > The VNC Enterprise Edition server supports GLX > out-of-the-box, using the Mesa software renderer, so if > you're not averse to pay-for software then you might try > that. I have no problem with paying for software. But we need the source code to make some small, but important changes. Does the Enterprise Edition come with sources? We don't need to redistribute them. A restricted license, which allows us to run a single modified vncserver, is sufficient for our business. How does the licensing of TightVNC and RealVNC work? Don't they use parts of the xfree86 or x.org projects, which are controlled by GPL or LPGL? > For VNC Free Edition & TightVNC servers, probably the > easiest way to get GLX support is to use VirtualGL. It > does require that apps access GLX via libGL, and that the > console graphics card supports "pbuffers" (off-screen render > buffers, essentially), but it's reasonably straightforward > to set up. Thanks. I did not fully understand the VirtualGL installation at this moment. The important question is, whether one can connect with any recent VNC viewer. Or is some special client required? Thank you Heiko ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___________________________________________________________ TightVNC mailing list, VNC-Tight-list@... To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list |
|
|
|
Re: Enable BuildGlxExt (to avoid errors 'Xlib: extension "GLX" missing on display ":1.0"')
by James Weatherall-2
::
Rate this Message:
Heiko,
[snip] > I have no problem with paying for software. But we need the source code to make some small, but important changes. Does the Enterprise Edition come with sources? We don't need to redistribute them. A restricted license, which allows us to run a single modified vncserver, is sufficient for our business. VNC Enterprise Edition does not come with source code, no. The X.Org server source has historically been distributed under an MIT, BSD or X Consortium license, rather than the GPL, I believe. > How does the licensing of TightVNC and RealVNC work? Don't they use parts of the xfree86 or x.org projects, which are controlled by GPL or LPGL? > >> For VNC Free Edition & TightVNC servers, probably the >> easiest way to get GLX support is to use VirtualGL. It >> does require that apps access GLX via libGL, and that the >> console graphics card supports "pbuffers" (off-screen render >> buffers, essentially), but it's reasonably straightforward >> to set up. > > Thanks. I did not fully understand the VirtualGL installation at this moment. The important question is, whether one can connect with any recent VNC viewer. Or is some special client required? VirtualGL can be used in a mode whereby it hands off GLX rendering to the console display's graphics hardware, and then renders the results to the Xvnc server using normal 2-D graphics APIs, for delivery to viewers in the normal way. HTH, -- Wez @ RealVNC Ltd ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___________________________________________________________ TightVNC mailing list, VNC-Tight-list@... To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list |
| Free embeddable forum powered by Nabble | Forum Help |
