Re: How to fix broken security in Windows 2000?

From: Karl Levinson, mvp (levinson_k_at_despammed.com)
Date: 02/06/05

  • Next message: Karl Levinson, mvp: "Re: How to fix broken security in Windows 2000?"
    Date: Sun, 6 Feb 2005 17:41:57 -0500
    
    

    "Shannon Jacobs" <shanen@my-deja.com> wrote in message
    news:eIyF5S%23CFHA.2756@TK2MSFTNGP12.phx.gbl...

    > from there. Many years ago the newsgroups had a positive SNR, but nowadays
    > zero-signal-and-downhill is the safe prediction.
    >
    > Just in case some technically competent person would be so kind as to
    > provide a useful answer, the technical question is:
    >
    > How can missing security certificates be identified (and "safely"
    replaced)?

    As I said, the first link I posted, which you complained about, tells you
    EXACTLY how to do that. If the instructions in that link didn't work for
    you, please tell us what the results are, e.g. you tried everything on that
    list, and X happened or didn't happen. If you had tried everything on that
    list, you would now be able to tell us that your computer has all the
    relevant certificates, and we would then know that the problem has nothing
    to do with restoring deleted certificates as you still seem to believe. We
    could also rule out a number of other dependencies on file checking besides
    certificates, and move towards the real cause and solution.

    I thought you said in a previous post that you had fixed the problem, and
    pointed to a page that suggested you might have re-installed some MS patch
    or another.

    > experiences, I do believe I could escalate the issue, pay Microsoft some
    > "support" money, and someone at Microsoft would reveal the answer, perhaps

    Phone support for problems caused by MS patches [which you blamed at times]
    is absolutely free. What more could you possibly want? Which other vendors
    do this for you? You might be charged if the problem was not due to a MS
    patch.

    > with a clause requiring me not to republish it in public places like the
    > newsgroups. After all, security almost entirely depends on obscurity, as
    all
    > good Microsoftians "know".

    Paranoia and FUD. The MS KB is the same one the paid MS support technicians
    use.

    [I trimmed the rest of the huge post below as a courtesy to other readers
    here.]


  • Next message: Karl Levinson, mvp: "Re: How to fix broken security in Windows 2000?"

    Relevant Pages

    • Re: How to fix broken security in Windows 2000?
      ... to do with restoring deleted certificates as you still seem to believe. ... pointed to a page that suggested you might have re-installed some MS patch ... Phone support for problems caused by MS patches ... The MS KB is the same one the paid MS support technicians ...
      (microsoft.public.windowsupdate)
    • Re: How to fix broken security in Windows 2000?
      ... to do with restoring deleted certificates as you still seem to believe. ... pointed to a page that suggested you might have re-installed some MS patch ... Phone support for problems caused by MS patches ... The MS KB is the same one the paid MS support technicians ...
      (microsoft.public.win2000.security)
    • Re: How to fix broken security in Windows 2000?
      ... to do with restoring deleted certificates as you still seem to believe. ... pointed to a page that suggested you might have re-installed some MS patch ... Phone support for problems caused by MS patches ... The MS KB is the same one the paid MS support technicians ...
      (microsoft.public.win2000.windows_update)
    • Re: Is Zotob A MS Plot . . . .
      ... > service provider paid $150,000 to patch their operating system. ... > Even though the IT firm would pay nothing to Microsoft to upgrade to ... > pay those hourly technicians to "touch" a helluva lot of machines. ...
      (microsoft.public.windowsxp.general)
    • Re: include page
      ... Lesa ... >> My ISP's suggestion that I apply the patches to the server myself is ... >> Our Technicians response to your ticket is as follows ... >> Due to the nature of our packaging system, we cannot patch the existing ...
      (microsoft.public.frontpage.client)