Encrypted passwords for Java viewer

Both the Windows and UNIX version of vncviewer can take an encrypted 
password as argument. The Java viewer cannot. The included patch adds the 
option ENCPASSWORD, which fixes this problem. 

-- 
Peter Åstrand                Telephone: +46-13-21 46 00
Cendio Systems               E-mail: peter <at> cendio.se
Teknikringen 3
583 30 Linköping
Sweden

diff -u tightvnc_javasrc.org/VncViewer.java tightvnc_javasrc/VncViewer.java
--- tightvnc_javasrc.org/VncViewer.java	Thu Feb 14 16:19:10 2002
+++ tightvnc_javasrc/VncViewer.java	Mon Apr 15 18:00:53 2002
 <at>  <at>  -68,6 +68,7  <at>  <at> 
   String host;
   int port;
   String passwordParam;
+  String encPasswordParam;
   int deferScreenUpdates;
   int deferCursorUpdates;
   int deferUpdateRequests;
 <at>  <at>  -201,6 +202,25  <at>  <at> 
       return;
     }
 
+    // Encrypted password via ENCPASSWORD
+    if (encPasswordParam != null) {

Fullscreen, KDE and focus

The vncviewer for UNIX does not work with the KDE window manager in 
fullscreen. When starting the viewer with the -fullscreen option, the 
focus in given to the application active before starting vncviewer. All 
keyboard events are reported to this application, instead of vncviewer. 

Changing:

XSetInputFocus(dpy, PointerRoot, RevertToPointerRoot, CurrentTime);

to:

XSetInputFocus(dpy, DefaultRootWindow(dpy), RevertToPointerRoot, 
CurrentTime);

...in fullscreen.c seems to fix the problem. 

Another bug: When running vncviewer in fullscreen with a framebuffer
smaller than the display, vncviewer makes black borders around the desktop
in the middle. If the mouse pointer is outside the desktop, over the black 
border, keyboard events are not propagated. Also, the F8 menu does not 
work. 

This can be fixed by grabbing the keyboard. 

The included patch fixes both these two problems. For some reason, the 
grabbing seems not to work after toggling from non-fullscreen to 
fullscreen mode. I have no idea why. 

I have also experienced some fullscreen problems with Sawfish: The window

Best, Fast, and Listen Compression Modes -- Trying Again.

> Hi,
> 
No response to my first post of this question, so I'll try again, just in
case everyone missed it.

> I am a newbie, and have been unable to find any documentation on the above
> modes.
> 
> Would someone be kind enough to explain them? We're monitoring a number of
> NT workstations from Win98 machines, and I'm interested in the fastest,
> most reactive mode possible (along with any other tweaks that will provide
> this performance aside from mode choice).
> 
> Thanks,
> Tony

___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

TightVNC 1.2.3 compiler trouble on IRIX 6.5.6m

Hello,

I'm trying to build v1.2.3 on an SGI O2 running IRIX 6.5.6m. I fixed most
trouble using Ellis Golub's suggestions on the VNC mailing list (dated Jun
27 2001). I used the package with zlib and jpeglib because the default
jpeglib in 6.5.6 is probably not adequate (too old). 

Bulding the vnc-tools went fine. However, building Xvnc didn't. I used the
command 

------------------------------------------------------------------------
	make BOOTSTRAPCFLAGS=-DFIXUP_CPP_WHITESPACE World
------------------------------------------------------------------------

as suggested by Ellis, but after a couple of minutes (and a lot of warnings)
I encounter the next error:

------------------------------------------------------------------------

  ...

cc -c -O -xansi -mips3 -n32  -I. -I../../../../exports/include/X11
-I../../../../include/fonts -I../../../../exports/include/X11
-I../../cfb -I../../mfb -I../../mi -I../../include -I../../os
-I../../../../../include -I../../../../../lib/zlib -I../../../../../lib/jpeg
-I../../../.. -I../../../../exports/include  -DSVR4 -DSHAPE
-DNEED_LINEHELPER -DINCLUDE_ALLOCA_H -DNDEBUG   -DFUNCPROTO=7 -DNARROWPROTO
-DDDXTIME  cursor.c
`all' not remade because of errors (bu14)
don't know how to make hw/vnc/libvnc.a (bu42).

Re: Best, Fast, and Listen Compression Modes -- Trying Again.

This one time, at band camp, Booth, Tony said:

> > Hi,
> > 
> No response to my first post of this question, so I'll try again, just in
> case everyone missed it.
> 
> > I am a newbie, and have been unable to find any documentation on the above
> > modes.
> > 
> > Would someone be kind enough to explain them? We're monitoring a number of
> > NT workstations from Win98 machines, and I'm interested in the fastest,
> > most reactive mode possible (along with any other tweaks that will provide
> > this performance aside from mode choice).
> > 
> > Thanks,
> > Tony

the default install of TightVNC 1.2.3 (win32) creates these shortcuts in
the TightVNC start menu:
	TightVNC Viewer (Best Compression)
	TightVNC Viewer (Fast Compression)
	TightVNC Viewer (Listen Mode)

best compression simply launches the viewer with these command line
options:
	 -compresslevel 9 -quality 0
fast compression:
	 -encoding hextile

Re: Fullscreen, KDE and focus

On Thu, Apr 18, 2002 at 11:26:26AM +0200, Peter Åstrand wrote:

> The included patch fixes both these two problems.

Excellent!  Thanks for fixing this.

Tim.
*/

Ports of TightVNC

Hi,

We have succesfully ported TightVNC for multiple unix platforms. Who do
I need to contact to get these archives posted on tightvnc.com?

AIX-4.2
Compaq-Tru64-V5.0A
Compaq-Tru64-V5.1
Digital-UNIX-V4.0D
Digital-UNIX-V4.0E
Digital-UNIX-V4.0F
HP-UX-11.00B
Linux-244
SunOS-5.6_sparc
SunOS-5.7_i386
SunOS-5.7_sparc
SunOS-5.8_sparc

Thanks,

Matt

--

-- 
Matt Shine-Sanders        | e: mshine <at> kinetworks.com
Systems Administrator     | w: 919.468.5886 x267
Ki Networks, Inc.         | c: 919.931.2217

This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient or have received this e-mail in
error, notify the sender immediately and destroy this e-mail. Any

VNC-Tight & Fluxbox

>Hello All,

After I vnc into the machine I type fluxbox for my WM but I get a core 
dump! I am not having a problem with vnc just the fluxbox wm. I am hoping 
someone on this list has seen/fixed this before. I am searching & googleing 
but to no avail.

Here is the exact message after a start fluxbox:

BScreen::BScreen: managing screen 0 using visual 0x22, depth 32
fluxbox: signal 8 caught
aborting... dumping core
Aborted

KDE, twm & enlightenment all start fine after I vnc in. Only fluxbox is 
giving me problem and I really am diggin fluxbox over the other WM out 
there. Fluxbox runs fine from the terminal just not from a vnc session. I 
am using tightvnc client & server.

Thanks for taken a look!

Mike

Thank You and have a nice day!

Regards,

Mike Ickes
mickes <at> digithedz.com

TightVNC over SDL!

I've starting patching a copy of TightVNC to run on top of SDL.  This 
*greatly* simplifies the code and it's pretty fast too.  I've got video 
and mouse working, but haven't had a chance to start hacking in the 
keyboard support.  Because SDL runs on top of DirectInput, I should be 
able to catch alt-tabs and other key combos that don't normally get 
sent.  I should also be able to put together a true full-screen mode. 
 Didn't take long- you guys have done an awesome job in coding it so 
that I could put this stuff in without any trouble.

Any interest?  I could probably use some beta testers as well.  If 
there's interest, I could put together a real release.

___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

Re: TightVNC over SDL!

I am very interested as this would solve my main problem with the Unix
VNC client, the fact that the screen is not double buffered.  Not being
double buffered means that minimizing and restoring the client causes
the client to pull the entire screen back from the server.  

Please let me know when I can test this code.

On Sat, 2002-04-20 at 16:14, Matthew Mastracci wrote:
> I've starting patching a copy of TightVNC to run on top of SDL.  This 
> *greatly* simplifies the code and it's pretty fast too.  I've got video 
> and mouse working, but haven't had a chance to start hacking in the 
> keyboard support.  Because SDL runs on top of DirectInput, I should be 
> able to catch alt-tabs and other key combos that don't normally get 
> sent.  I should also be able to put together a true full-screen mode. 
>  Didn't take long- you guys have done an awesome job in coding it so 
> that I could put this stuff in without any trouble.
> 
> Any interest?  I could probably use some beta testers as well.  If 
> there's interest, I could put together a real release.
> 
> 
> 
> ___________________________________________________________
> TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list