Re: Can't disable "Trusted" for Certificates Issued by MS Certificate Server

From: Ohaya (ohaya_at_cox.net.NO_SPAM)
Date: 10/27/03 

Date: Mon, 27 Oct 2003 17:50:46 -0500

Hi,

Does anyone know how I can report this as a potential bug to Microsoft?

FYI, I happen to have imaged my Windows 2K Server partition immediately
after installing Windows, AD, IIS, and Certificate Manager, and before doing
anything else.

I've confirmed that with a fresh restore from the abovementioned image, the
problem that I described in my original post already exists.

Please advise....

"Ohaya" <ohaya@NO_SPAM.cox.net> wrote in message
news:3F9D3A7F.7294A454@NO_SPAM.cox.net...
> Hi,
>
> I think that I have encountered a somewhat serious "bug" somewhere. I
> can't tell if it's a CryptoAPI bug, an IIS bug, or whatever, so I'm
> cross-posting this to several newsgroups. This seems like (to me) a
> rather serious problem, and I'll try to describe what's happening as
> best I can, and also provide a somewhat kludgy workaround.
>
>
> Background:
> ===========
> Server: Win2K Advanced Server SP4, updated on Friday (10/24/03)
> Server is the DC (i.e., ActiveDirectory is installed)
> MS Certificate Server is installed
> IIS5
>
> Client: Win2K Pro SP4, updated same date as server
> IE 6.0.2800.1106
>
>
> I have been preparing to configure the above server for SSL with server
> and client authentication for awhile.
>
> Before I did that, in order to do some pre-testing, I issued a server
> cert for IIS with MS Certificate Server, and several client certs.
>
> I got all of this (SSL with client and server authentication) working,
> including IE would display the client certs that were issued by MS
> Certificate Server whenever I tried to connect from IE to IIS.
>
>
> Then, using the IIS server certificate wizard, I deleted the original MS
> Certificate Server-issued server cert, then created a new server
> certificate request, which I then sent to my commerical CA one night.
> The next morning, I received the new server cert from my commercial CA,
> along with a set of test client certificates.
>
> I then installed the root cert from my commercial CA on the server, and
> then using IIS, used the IIS server certificate wizard to install the
> new server cert that I had just received from my commercial CA.
>
> I also installed one of the test client certificates from my commercial
> CA, and installed it on my client machine, and began testing.
>
>
> Problem:
> ========
> From some previous testing with an earlier similar (SSL client and
> server authentication) setup, I found that I could control which client
> certificates that IE would display, when connecting to the server, by
> enabling or disabling the "Client Authentication" Purpose in the root CA
> certificate Purposes for specific root CAs.
>
> In other words, if I disabled/unchecked the "Client Authentication"
> purpose for the root CA cert for "Whatever CA", then client certificates
> issued by "Whatever CA" would display in the IE popup when I tried to
> connect to the server. If I enabled/checked the "Client Authentication"
> purpose for the root CA cert for "Whatever CA", then client certificates
> issued by "Whatever CA" would NOT display in the IE popup when I tried
> to connect to the server.
>
>
> However, it appears that with the setup that I ended up with above
> (install MS Cert Server server cert, uninstall server cert, install new
> commercial CA server cert), which I described above under "Background",
> this (enabling/disabling "Client Authentication" purpose for the root CA
> cert) does not appear to work for the client certs created with MS
> Certificate Server.
>
> Specifically, the client certificates that I created using MS
> Certificate Server still get displayed by IE when connecting to the
> server, regardless of how the "Client Authentication" purpose is set in
> the root CA certificate on the server-side, and there does not appear to
> be any reasonable way to prevent these client certificates from being
> displayed by IE during a connection attempt.
>
>
> I'm guessing (I would HOPE) that deleting the root certificate for my MS
> Certifate Server on the SERVER might work, but then that would kill my
> MS Certificate Server installation, so that doesn't seem like a
> reasonable solution, and really, I'm kind of puzzled about why the
> "Client Authentication" purpose is "obeyed" for all client certificates
> except for the ones created by MS Certificate Server.
>
>
> Bottom line: It appears that if you install MS Certificate Server,
> issue a server cert and some client certs, then install a server cert
> from another CA, that there is no way way get IE browsers that had
> client certs from MS Certificate Server not to display those previously
> issued client certs.
>
>
>
> Possible workaround:
> ====================
> I haven't found a way, from the server-end, to cause IE not to display
> those MS Certificate Server-issued client certs, but thankfully, with
> IIS at least, the CTL functionality still works properly.
>
> In other words, if I set up a CTL with only the root cert from my
> commercial CA, IE will STILL DISPLAY both the client certs from my
> commercial CA and the client certs that were issued by MS Certificate
> Server, but at least the authentication/connection will fail if someone
> tries to connect using one of the client certs issued by MS Certificate
> Server.

Relevant Pages

  • Re: Web Certificate for IIS Server on SBS Domain
    ... Before your reply, I actually ran across rapidssl myself, and have ordered and installed the free 30-day certificate on my site. ... I explained what you'd told me about putting my existing configuration at risk by installing Cert Services, and he said he didn't know that. ... Again, if you're just needing a cert to install on your web server to provide SSL connectivity for remote users, go with an external third-party provider. ... When you add Certificate Services on an internal network, lots of internal communications will start using pieces provided by the Cert Server instead of the defaults from Server 2003, and when things blow up, they can blow up gloriously. ...
    (microsoft.public.windows.server.sbs)
  • Re: Activesync between Windows Mobile 5 and SBS2003 gives error
    ... If you don't find a cert here that matches the URL for OWA, you need to re-run the CEICW wizard on the SBS box and re-create the self signed cert. ... I exported the certificate straight from the server. ... Treo 700wx running Windows Mobile 5. ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Services over a VPN
    ... Create a certificate request and submit it to godaddy in order to obtain a public cert. ... You can use the wizard in IIS Manager for this by creating a new website that matches the above name (on your TS server), right-click and choose properties, directory security tab, server certificate button. ... After the install you can stop or delete the website created above since you don't need it for anything. ...
    (microsoft.public.windows.terminal_services)
  • This is Definitely a BUG!! Re: Cant disable "Trusted" for Certificates Issued by MS Certi
    ... purpose of the root certificate for MS Certificate Server, IIS is ALWAYS ... >> cert for IIS with MS Certificate Server, and several client certs. ...
    (microsoft.public.win2000.security)
  • Re: SBS 2003 Premium and Cert Services
    ... that philosphy got blown out of the equation when SBS included Exchange OWA ... "Small Business Server" which is MS claim as to why the risk of exposing the ... the Certificate Server on another server, ... >> Cert, or you could edit the properties of your Certification Authority to ...
    (microsoft.public.windows.server.sbs)