admin | 1 Mar 2003 11:32
Picon

newbie: redhat 8.0

someone has built an .rpm package for this distro? (i'm not able to do
by myself).
thanks.
marco

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

Michael D. Setzer II | 1 Mar 2003 14:23

Stunnel options for tightvnc

The below is what I have done to get the stunnel to work. 
The system client machine using 127.0.0.1 to go thru the Stunnel to
connect to the host machine. 

In looking at the example from the one page, it has command line options 
that don't seem to work with the latest version of the stunnel. 

If someone has a clearer ideal of this, or perhaps other options.
I've used this on a windows 98 to Windows 98 connection, and a 
Windows 98 to a Windows NT 2000 server.

Server STUNNEL.CONF

 client = no
 cert = stunnel.pem

 [vnc]
 accept = 7777
 connect = 5900

CLIENT STUNNEL.CONF
 client = yes
 cert = stunnel.pem

 [vnc]
 accept = 5900
 connect = hostip:7777

+----------------------------------------------------------+
  Michael D. Setzer II -  Computer Science Instructor      
(Continue reading)

Nicholas Basso | 2 Mar 2003 07:38
Picon
Favicon

Re: Stunnel options for tightvnc

I'd like to confirm, did you do this with the standard configuration or did
you ever build your own pem file?  If you did it with the standard, were
there any special measures you had to take to get this to work?  I'd like to
write up an HTML walkthrough for Stunnel-izing your VNC because since
Stunnel is free for both linux and windows it's an extremely useful tool for
all users since everyone should have at least SOME protection
----- Original Message -----
From: "Michael D. Setzer II" <mikes <at> kuentos.guam.net>
To: <vnc-tight-list <at> lists.sourceforge.net>
Sent: Saturday, March 01, 2003 8:23 AM
Subject: Stunnel options for tightvnc

> The below is what I have done to get the stunnel to work.
> The system client machine using 127.0.0.1 to go thru the Stunnel to
> connect to the host machine.
>
> In looking at the example from the one page, it has command line options
> that don't seem to work with the latest version of the stunnel.
>
> If someone has a clearer ideal of this, or perhaps other options.
> I've used this on a windows 98 to Windows 98 connection, and a
> Windows 98 to a Windows NT 2000 server.
>
>
>
> Server STUNNEL.CONF
>
>  client = no
>  cert = stunnel.pem
>
(Continue reading)

Michael D. Setzer II | 2 Mar 2003 08:31

Re: Stunnel options for tightvnc

I just downloaded the Stunnel 4.04 from the stunnel.org and the 
.pem file from the same sight. No changes to anything. 

So, it is the standard stuff just using the stunnel.conf instead of the 
switch settings I found on a site. 

I would like to know more about the .pem file, and how to make a 
special one. 

On 2 Mar 2003 at 1:38, Nicholas Basso wrote:

From:           	"Nicholas Basso" <gedrean <at> yahoo.com>
To:             	<vnc-tight-list <at> lists.sourceforge.net>
Subject:        	Re: Stunnel options for tightvnc
Date sent:      	Sun, 2 Mar 2003 01:38:28 -0500

> I'd like to confirm, did you do this with the standard configuration or did
> you ever build your own pem file?  If you did it with the standard, were
> there any special measures you had to take to get this to work?  I'd like to
> write up an HTML walkthrough for Stunnel-izing your VNC because since
> Stunnel is free for both linux and windows it's an extremely useful tool for
> all users since everyone should have at least SOME protection
> ----- Original Message -----
> From: "Michael D. Setzer II" <mikes <at> kuentos.guam.net>
> To: <vnc-tight-list <at> lists.sourceforge.net>
> Sent: Saturday, March 01, 2003 8:23 AM
> Subject: Stunnel options for tightvnc
> 
> 
> > The below is what I have done to get the stunnel to work.
(Continue reading)

Constantin Kaplinsky | 2 Mar 2003 19:37
Picon

Re: Problems Installing TightVNC on Red Hat 8.0

Hello Andrew,

>>>>> "AHK" == "Kaplan, Andrew H." <AHKAPLAN <at> PARTNERS.ORG> writes:

AHK> Hello Constantin, The question you asked is what I am striving
AHK> for with TightVNC. What I am trying to do is have the remote
AHK> desktop session occur exclusively via an SSH tunnel. All
AHK> non-encrypted sessions will be disallowed.

AHK> I have installed the ssh daemon on the linux server. 
AHK> Additionally, I have configured the VNC server to automatically
AHK> start during the server boot by using the /etc/rc.d/rc.local
AHK> file. Currently the file contains the following line:

AHK> su ahk -c /usr/bin/vncserver :2

AHK> If I understand you correctly, in order for me to connect
AHK> strictly through ssh, the above line should be modified to read
AHK> as follows:

AHK> su ahk -c /usr/bin/vncserver -localhost :2

AHK> The clients that I am using are generally Windows 2000 and Linux
AHK> clients that have ssh installed on them. The Windows clients use
AHK> one of the following programs:
AHK> 1. puTTY
AHK> 2. QVTNet
AHK> 3. SSH Secure Client

AHK> Will TightVNC automatically interact with any of these programs,
(Continue reading)

Constantin Kaplinsky | 2 Mar 2003 19:37
Picon

Re: tightvnc on dual nic systems

Hello,

>>>>> "o" == "ocelot" <ocelot_ <at> fastmail.fm> writes:

o> i am left unable to vnc connect with a server running 98se that is
o> acting as a router connected to a lan (fixed ip) and the internet
o> (a dhcp dsl connection through a westell pass through bridge modem
o> ) that i can ftp into but not vnc.

o> any ideas?

I'm not sure how Win98 performs routing in your case. Maybe ftp is
working because there is a special masquerading facility for ftp, I
don't know. In any case, with static IPs, all you have to do is to
forward specific ports (e.g. 5900) on the router between network
interfaces.

--

-- 
With Best Wishes,
Constantin

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

(Continue reading)

Constantin Kaplinsky | 2 Mar 2003 19:37
Picon

Re: Clipboard transfer & jumping Mousecursor in TightVNC 1.2.8 (Win)

Hello Bruno,

>>>>> "BH" == Bruno Holliger <bh <at> swix.ch> writes:

BH> Hello! I experienced a small problem while copying several lines
BH> of text (divided by carriage returns and linefeeds) from the
BH> client (viewer) to the server: The carriage returns (chr(13)) are
BH> left out.

BH> On slow connections it happened that the mousecursor is jumping. 
BH> That means it is shown a few pixels to much left than it actually
BH> is. (This behaviour is only in the version 1.2.8).

Thank you, I've added two items to the bug tracker. I hope to test the
issues and fix them if possible, when time will permit.

--

-- 
With Best Wishes,
Constantin

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

Nagios User | 3 Mar 2003 21:50

Delay when logging out on Windows 2000 with TightVNC running.

Hi,

Platform: Windows 2000 Professional SP3
TightVNC: 1.2.8

Symptom:
When logging out (or shutting down) there is a 60 second delay with a dialog
box that says "Saving your settings...".  If I shutdown the VNC service
before logging out, the system logs me out almost immediately.  Apparently
there is something that VNC is waiting on before allowing Win2k to log you
out.

Note that this symptom appears when I am physically at the system I am
logging out.  Don't know what happens when I'm connected remotely.

Note also that I DID do something fairly stupid at one point.  I had VNC
loaded and without thinking, loaded pcAnywhere to connect remotely to a
system I needed to test something on.  I started noticing the problem after
I INSTALLED pcAnywhere and the problem persisted even after I uninstalled
pcAnywhere.

I also uninstalled VNC and when I reinstalled VNC the problem reoccurred.  I
then uninstalled VNC and went through the registry and deleted all of the
keys that the VNC uninstall left and then reinstalled and the same problem
happened again.

Sorry for the long message, but wanted to brain dump everything I have
already tried...

Thanks for any help,
(Continue reading)

Robert A LaRock | 4 Mar 2003 07:02

Robert A LaRock/SAHesperia is out of the office.


I will be out of the office starting  03/03/2003 and will not return until
03/07/2003.

I will respond to your message when I return.

Bob

-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com
___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

G.Lyons | 4 Mar 2003 09:45
Picon
Favicon

Remove me please

could you take me off the mailing list

Gmane