HP3000-L Archives

October 2001, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Pete Osborne <[log in to unmask]>
Reply To:
Pete Osborne <[log in to unmask]>
Date:
Mon, 1 Oct 2001 20:49:03 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Hmmm. Now how exactly does that work?

As I understand it.... When I connect to a site over https, I receive their
certificate or public key. When I send data to the site, it is encrypted
using their public key and can only be unencrypted by their private key which
they keep locked away with a PEM phrase & restrictive permissions. Now, how
exactly is the data that is sent to my browser efrom the web server
encrypted? How does my browser unencrypt it?

-Pete

On Monday 01 October 2001 17:22, Mark Bixby wrote:
> Both directions of the TCP stream are encrypted by SSL (i.e. both the
> GET/POST/etc HTTP request sent to the server by your browser, and the
> results sent back to your browser by the server).
>
> - Mark B.
>
> Peter Osborne wrote:
> > Here's a question about SSL enabled web servers, such as WebWise. I would
> > like to know, when data is transfered over https, is the data secure in
> > both directions (downstream & upstream) or is only the data submitted
> > back (upstream) to the web server encrypted.
> >
> > I believe it is the latter but I thought I'd ask.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2