[dba-Tech] Tight VNC Options

A word of caution w/ VNC, there is a known exploit w/ older versions
of VNC that allows an attacker to gain complete access to the machine
in question.  Our network right now was attacked a few months ago, the
hacker left behind several pices of code that were not readily
identified by either a/v/malware software. etc.  result he was able to
get back in via a network of VNCe'd machines.  Our new corp policy now
forbids VNC (any flavor) tho the problem now has been patched.




On 11/27/06, JWColby <jwcolby at colbyconsulting.com> wrote:
> Stuart,
>
> Thanks for that.  I went in to the shortcut and surprise, it already has the
> compression stuff set to something, all I had to do was experiment for what
> works for me.
>
> Thanks for pointing that out.
>
> John W. Colby
> Colby Consulting
> www.ColbyConsulting.com
>
> -----Original Message-----
> From: dba-tech-bounces at databaseadvisors.com
> [mailto:dba-tech-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
> Sent: Sunday, November 26, 2006 11:30 PM
> To: Discussion of Hardware and Software issues
> Subject: Re: [dba-Tech] Tight VNC Options
>
> On 26 Nov 2006 at 23:12, JWColby wrote:
>
> > How do I set options in the viewer and keep them the next time the
> > viewer opens?  I want to use compression, but the 0 level really
> > sucks.  I set to 9 (best quality) but when I close, the next time I
> > open the viewer I am back to 0.
>
> Try setting up shortcuts to it using using commandline options
>
> "C:\Program Files\TightVNC\vncviewer.exe" -compresslevel 9 -quality 0
>
> >From http://www.tightvnc.com/vncviewer.1.html:
>
> -compresslevel level
>     Use specified compression level (0..9) for "tight" and "zlib" encodings
> (TightVNC-specific). Level 1 uses minimum of CPU time and achieves weak
> compression ratios, while level 9 offers best compression but is slow in
> terms of CPU time consumption on the server side. Use high levels with very
> slow network connections, and low levels when working over high- speed LANs.
> It's not recommended to use compression level 0, reasonable choices start
> from the level 1.
>
> -quality level
>     Use the specified JPEG quality level (0..9) for the "tight" encoding
> (TightVNC-specific). Quality level 0 denotes bad image quality but very
> impressive compression ratios, while level 9 offers very good image quality
> at lower compression ratios. Note that the "tight" encoder uses JPEG to
> encode only those screen areas that look suitable for lossy compression, so
> quality level 0 does not always mean unacceptable image quality.
> _______________________________________________
> dba-Tech mailing list
> dba-Tech at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-tech
> Website: http://www.databaseadvisors.com
>
> _______________________________________________
> dba-Tech mailing list
> dba-Tech at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-tech
> Website: http://www.databaseadvisors.com
>


-- 
-Francisco
http://sqlthis.blogspot.com | Tsql and More...