Re: X509 and SSL

From: Softwaremaker (msdn_at_removethis.softwaremaker.net)
Date: 10/20/04


Date: Wed, 20 Oct 2004 19:41:34 +0800

When you enable SSL / HTTPS on a particular folder, you are effectively
encrypting the transport layer from client to your server for pages of that
particular folder.
ALL content on that transport channel is encrypted, regardless of whether
its HTML, XML or SOAP. This is achieved through a Handshake Protocol which
exchanges asymmetric keys and challenge messages amongst others until a
shared secret (Symmetric Key) is achieved. Thereafter anything that goes
along this channel gets encrypted with this shared secret (Symmetric Key).

I could sit here and talk about the Handshake Protocol of SSL / HTTPS but
this is not the right newsgroup to do it and it would take too long ;)

There can be good and bad things with SSL. Tremendous overheads is one.
Another is, you are authenticating via machines, not users.

If you need to authenticate your clients via signatures, you may need client
certs which may NOT be feasible. DO TAKE NOTE tho, you are authenticating
requests via machines, not user, if you invoke SSL / HTTPS.

Singapore Coffee == Starbucks Coffee; Brazilian Cofee;
In other words, we import them like it is since we cannot grow them here :)

It is a different answer if you ask about food, that, my friend, it is a
paradise here.

-- 
Thank you.
Regards,
Softwaremaker
http://www.softwaremaker.net/blog
=========================================
"andrea" <a.canade@retis.it> wrote in message
news:5c884a8f.0410200209.1e519a7c@posting.google.com...
> > > must i buy one certificate for sign response messages and one
> > > certificate to enable IIS
> > >
> > > or can i buy one certificate and configure IIS too?
> > >
> > > thank you for patience i'm a newbie on https and digital signing... i
> > > know :)
> > > andrea
> >
> > One certificate is sufficient is you don't need to identify the signing
> > application distinctly from the web server.
>
> [Andrea]
> SoftwareMaker correct me if i'm wrong,
> you tell me that i can buy only one certificate for signing server
response
> and that certificate must contain the  SSL-Enabling feature
>
> with this "feature" i can configure an https envinronment on IIS and
> receive unsigned requests from clients
> and send signed response messages  from webservice to clients
>
> right?
>
> ehm..
> I 've received no response about Singapore coffee quality :-)
> maybe i really came to visit you ;-)
>
> thanks a lot
> andrea


Relevant Pages

  • Re: IE https certificate attack
    ... How non-interactive ssl clients in EAI and web services software handle ... Subject: IE https certificate attack ...
    (Vuln-Dev)
  • Lost in a sea of information (SSL Configuration)
    ... to configure SSL on my Exchange Server in order for users to access OWA ... using https, but apparently I'm not doing something right. ... I installed the Certificate Services on the server and completed the fields ...
    (microsoft.public.exchange2000.admin)
  • Re: Intermittent SSL connection problems with IIS6 on Windows 2003 R2 SP2
    ... Are you saying that those people who can't view the https default page can always view the http default page, or is it something more than that? ... Some of our clients have no problem using the https version. ... certificate issue, as otherwise no-one would be able to see the site. ... The clients experiencing problems have a mix of operating systems ...
    (microsoft.public.windows.server.general)
  • RE: Pocket PC 2003 Sych with Exchange Issue
    ... How Secure Sockets Layer Works ... SSL for the HTTP connections for these mobile features. ... HTTPS or not using HTTPS when you try to use Exchange 2003 OMA/Server ... certificate from an well-known third party CA or set up and issue your own ...
    (microsoft.public.windows.server.sbs)
  • Re: SSL and redirect
    ... Kevin, ... I pretty much locked down applications to https only, ... Any information that you found about using SSL would ... > that seems to favor the Web Server Certificate Wizard ...
    (microsoft.public.dotnet.framework.aspnet.security)