, 2003 5:06 PM
To: Exchange Discussions
Subject: RE: Kinda OT: OWA and SSL
We typically copy the certification path to the web server, create a link on
the page to the path and let the clients install the path from there. Waa
Laa. No more annoying pop-up box.
-Original Message-
From
Andy was PWI last night.
-Original Message-
From: Andy David [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 14, 2003 6:57 AM
To: Exchange Discussions
Subject: RE: Kinda OT: OWA and SSL
Sure. You know, like freedom fries, waa laa etc..
Well, it seemed funnier after a few glasses of wine
. :|
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ed Crowley
Sent: Friday, June 13, 2003 11:09 PM
To: Exchange Discussions
Subject: RE: Kinda OT: OWA and SSL
Waa Laa? Would that be the Anglicization of voila?
Ed Crowley MCSE+Internet MVP
Freelance E-Mail
Either.
- Original Message -
From: Scott Force [EMAIL PROTECTED]
To: Exchange Discussions [EMAIL PROTECTED]
Sent: Friday, June 13, 2003 10:31 AM
Subject: Kinda OT: OWA and SSL
I've setup OWA (5.5/6a) and I now want to secure it with SSL. I have a
stand alone 2000 server where IIS
In the ether?
-Original Message-
From: Andy David [mailto:[EMAIL PROTECTED]
Sent: Friday, June 13, 2003 8:35 AM
To: Exchange Discussions
Either.
- Original Message -
From: Scott Force [EMAIL PROTECTED]
To: Exchange Discussions [EMAIL PROTECTED]
Sent: Friday, June 13, 2003
Both will work. What you get with a third party cert is the assertion that
the server to which your clients are connecting is truly part of your domain
(i.e. traffic isn't being hijacked to a rogue server in order to steal
passwords, etc.)
With a cert from a homegrown server, your users will
FWIW we use Geotrust certs from rackshack.net - no idea how they can do it
but they're $39 and work just fine and do up to 128bit.
As I see it certs do two things, encrypt, and prove you are who you claim to
be, and to me the extra that Verisign and the likes cost isn't worth it for
what you
Hutchings
Sent: Friday, June 13, 2003 9:36 AM
To: Exchange Discussions
Subject: RE: Kinda OT: OWA and SSL
FWIW we use Geotrust certs from rackshack.net - no idea how they can do it
but they're $39 and work just fine and do up to 128bit.
As I see it certs do two things, encrypt, and prove you
We use our own certs for OWA. Since its just our employees hitting that
site (well lets say its our employees that should be hitting that site),
Im not so concerned that we are not endorsed by a 3rd party. We
prefer to pay the $700 (to Verisign) for the cert and use it on our
truly public sites.
Thanks for the input...something for me to investigate
-Original Message-
From: Paul Hutchings [mailto:[EMAIL PROTECTED]
Sent: Friday, June 13, 2003 9:36 AM
To: Exchange Discussions
Subject: RE: Kinda OT: OWA and SSL
FWIW we use Geotrust certs from rackshack.net - no idea how they can
To: Exchange Discussions
Subject: RE: Kinda OT: OWA and SSL
Both will work. What you get with a third party cert is the assertion that
the server to which your clients are connecting is truly part of your domain
(i.e. traffic isn't being hijacked to a rogue server in order to steal
passwords, etc
, June 13, 2003 7:42 PM
To: Exchange Discussions
Subject: RE: Kinda OT: OWA and SSL
While I agree that 3rd-party certs are easier to install/manage, I would
strongly disagree with your assertion that homegrown certs can not be made
trusted. That is really not true at all. If you have your CA setup
:06 PM
To: Exchange Discussions
Subject: RE: Kinda OT: OWA and SSL
We typically copy the certification path to the web server, create a link on
the page to the path and let the clients install the path from there. Waa
Laa. No more annoying pop-up box.
-Original Message-
From: [EMAIL
13 matches
Mail list logo
