connecting from the office to my home *solution*

[Angelo Sarto]

The difference will be that it will appear that you are mainitaing a
https session for as long as you leave the tunnel up.

I agree with kevin as well about if you are unsure then perhaps not.

Even pr0n is only 1's and 0's and they usually get upset if you move
those bits around at work.

On 5/5/05, Collins, Kevin  [MindWorks] <KCollins "at" chevrontexaco.com> wrote:
> I'm not really sure. If you are that concerned, maybe you shouldn't use
> it :)
> 
> I suspect its all going to look like a random bunch of bits...
> 
> Kevin
> 
> -----Original Message-----
> From: John Gray [mailto:johngray "at" usa.net]
> Sent: Thursday, May 05, 2005 9:36 AM
> To: Collins, Kevin [MindWorks]
> Cc: vnc-list "at" realvnc.com
> Subject: RE: connecting from the office to my home *solution*
> 
> Do you think they can they tell the difference in their scans as to
> whether my
> traffic is HTTPS or SSH, or would it all look the same to them?
> 
> ------ Original Message ------
> Received: Thu, 05 May 2005 12:31:27 PM EDT
> From: "Collins, Kevin  [MindWorks]" <KCollins "at" chevrontexaco.com>
> To: "John Gray" <johngray "at" usa.net>, "Scott C. Best" <sbest "at" best.com>,
> "John
> Aldrich" <JAldrich "at" covista.com>,   "Angelo Sarto"
> <angelosarto "at" gmail.com>Cc:
> vnc-list "at" realvnc.com
> Subject: RE: connecting from the office to my home *solution*
> 
> > If they are monitoring to that level, it will probably look like you
> are
> > doing a lot of HTTPS traffic to them. As both (HTTPS and SSH) are
> > encrypted, there's nothing much for them to see but byte counts...
> >
> > Kevin
> >
> > -----Original Message-----
> > From: John Gray [mailto:johngray "at" usa.net]
> > Sent: Thursday, May 05, 2005 8:22 AM
> > To: Scott C. Best; John Aldrich; Collins, Kevin [MindWorks]; Angelo
> > Sarto
> > Cc: vnc-list "at" realvnc.com
> > Subject: Re: connecting from the office to my home *solution*
> >
> > Thanks guys!
> >
> >   Okay, so, I setup an SSH server at home, and am using PuTTY at work
> to
> > create a tunnel.  I had to use port 443, as port 22 is blocked.
> Seeing
> > that I
> > had to use a tunnel, I decided to use RDC instead of VNC.  Viola!  It
> > works
> > like a charm.  Both RDC and VNC work great through the tunnel.
> >
> >   One last question: Anyone know if what I'm doing will look
> suspicious
> > to
> > network security and raise a flag, or will it just look like normal
> > traffic?
> >
> > Thanks again,
> > John
> >
> >
> > >
> > > On 5/3/05, John Gray <johngray "at" usa.net> wrote:
> > > > Setup:
> > > >
> > > > Home - WinXP Pro SP2 w/ RealVNC 4.1.6 Service via broadband router
> > > > Office - WinXP Pro SP2 via large corporate LAN
> > > >
> > > > Test:
> > > >
> > > > Everything works fine connecting from a friends house.
> > > > I can telnet my home from the office on the VNC port.  It
> connects,
> > > > however no RFB response.
> > > >
> > > > Problem:
> > > >
> > > > Using Client - After entering the server name, and clicking [OK],
> > > > I get "read: Connection reset by peer (10054)"
> > > >
> > > > Using Web - After entering the server name, and clicking [OK], I
> get
> > > > "rdr.IOException: java.net.SocketException: Socket read Failed"
> > > > _______________________________________________
> > _______________________________________________
> > VNC-List mailing list
> > VNC-List "at" realvnc.com
> > To remove yourself from the list visit:
> > http://www.realvnc.com/mailman/listinfo/vnc-list
> _______________________________________________
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list