Re: sslstream and certificates

From: Joe Kaplan \(MVP - ADSI\) (joseph.e.kaplan_at_removethis.accenture.com)
Date: 05/27/05 

Date: Fri, 27 May 2005 13:19:49 -0500

Actually, I think for what you are doing, it probably makes sense. You
would need to be using IIS to host ASP.NET which it doesn't sound like you
want to do.

I believe there is another model though that might be easier than using raw
TCP. In .NET 2.0, I believe there is a new HttpListener class that
interfaces directly with HTTP.SYS. This only works on Win2K3 and XP SP2 so
far (as they are the only ones with the required driver), but it might give
you a higher level of abstraction.

I'm way way out of my depth now, but I've heard others discussing this new
feature as a way to host your own web services and other HTTP services in
your own process without need ASP.NET.

Might be something worth checking out...

Joe K.

"Jakob Nielsen" <a@b.c> wrote in message
news:%23oZPgZuYFHA.2508@TK2MSFTNGP15.phx.gbl...
> >I guess I'm just not sure of what exactly it is you are doing. If your
> >goal is to have a WinForms app communicate with a web server
> >programmatically, .NET includes a System.Net.HttpWebRequest class that
> >you can use for doing programmatic HTTP protocol stuff, including SSL.
>
>> If your goal is to implement a custom HTTP Server, then it seems like it
>> would be easiest to using the built in model in ASP.NET and use its
>> extensibility mechanisms to implement your own HTTP handlers.
>>
>> However, if you really want raw stream based data that is SSL encrypted,
>> then SslStream is probably the way to go. It really depends on the
>> problem you are trying to solve and the level of abstraction you want.
>
> I have an application which is a normal winforms app. It acts as a
> backupserver and for that I want it to communitate with clients (that I
> also create) in a secure way. Ssl seems fine. I also want that server app
> to service users through a browser interface, so they can perform simple
> maintanence and status checks from anywhere without the actual backup
> client.
> That is also comunication which should be conficential, so https seems
> lige a good choice.
>
> Currently i have a tcplistener accepting connections on port 80, parsing
> http requests and sending back html formatede text and graphics. I do the
> http and html myself.
>
> Are you saying that I can grab a few classes from asp.net and use them
> here without needing some webserver to run it all? I guess that makes
> sence. The classes in asp.net which can read a http header and generate
> one, should work no matter where you run them.
>
>> Glad you are making progress anyway.
>
> Thanks. *singing* We all get byyyyy with a little help from our groups
> :-)
>

Relevant Pages

  • Re: RPC Over HTTP (External)
    ... Oh Ok no SSL ... causing the RPC proxy server not to trust the connection. ... i set use HTTP first for fast connection. ...
    (microsoft.public.exchange.admin)
  • Re: Kerberos error KDC_ERR_BADOPTION
    ... Ran the same test again using the IP instead of the host name and got this: ... Reusing existing connection \n ... Server: Microsoft-IIS/6.0\r\n ... I suggest you use webfetch to perform a test and trace the rawdata of http ...
    (microsoft.public.inetserver.iis.security)
  • Re: ModSSL - Knoppix 3.3
    ... NameVirtualHosts and SSL don't mix. ... This automatically pushes an incorrect http request to the secure host over ... > I create some server key & crt. ...
    (Focus-Linux)
  • Re: Security of IIS - Secure Intranet web site on SBS2003 box
    ... > take two days to rebuild their server and return everything to normal. ... > Before 'Code Red' IIS was considered reasonably secure. ... >> over HTTP via SSL for OUTLOOK-EXCHANGE links to users operating in the ...
    (microsoft.public.windows.server.sbs)
  • Re: Installing Certificates - Pulling My Hair Out
    ... Why would you do HTTP over ... the internet to the ISA Server then doe SSL tot he internal Web Server? ...
    (microsoft.public.isa.publishing)