Security certificate question: see details below?
552157
This is complex and messy if I cover the details. So I'll just hit the high spots. Follow along with this streamlined interaction. Remember that all anyone ever knows about the information received from the Internet is that it came from the Internet. It might be a spoof -- Coke sabotaging the Pepsi Web site -- or something less playfully amusing, like a site phishing for account and password information in preparation for soem identity theft. How to weed out some (but of course never all) of the scams?\n\n========\nhow it works (a sketch) \n\nSo. Your browser goes to a Web site. On your behalf, in order to avoid being spoofed by a fake site, it will attempt (*IF* its settings have told it to always do so) to ensure that the web server it's getting a page from is on the up and up. Since a browser is a collection of computer programs, it has no ability whatsoever to make estimates  about the validity of a Web server. (Software really is dumb as a box of rocks, and only does the right thing, or appears intelligent, because it's been carefully designed and programmed beforehand.) Accordingly, your browser relies upon something else to tell it about the Web site. And that something else is a Certificate Authority (which will be part of a Private Key Infrastructure -- a PKI). Certificate Authorities are usually, but not always, companies who have set up in business to provide this service for a fee. But certificates are produced by software, and with the right software, you (or anyone else) could produce your own. Whether anyone should rely on those for anything at all is something else altogether. \n\nThe only function of a CA is to vouch for some entity (in the case of a Web server, it's the operator of the server machine) as being who it claims to be. In the absence of such a certificate, the Web site might be OK, but no one is vouching for it. Or it might not. You can think of a CA's function as more or less that of a notary public, with similar benefits and problems. \n\nThe vouching is done via a Digital Identity Certificate sent to your browser by the site; this is a packet of data, protected cryptographically against alteration of any kind, containing the entity's identity information. Since anyone can generate such a certificate, how can your browser (and, by inference, you as well) rely on its claims about identity? The answer is that your browser already has a certificate for the CA itself which it can use to test (crytographically) whether the Web server's certificate has been is correct. If it is, your browser assumes everything is fine and proceeds. \n\nAnd how did it get the CA's certificate? Well, it was bundled with the browser itself by the browser maker (eg, Microsoft, the Firefox folk, the Norwegians who run the Opera business, ...). And was included in the browser's operating environment when the browser was installed on your computer. You trust that it's correct because of this history. Don't you? You didn't know anything about all this stuff? Most people don't and just proceed, hoping htat it will all work out right. \n\nAnd with that comes the skunk at the garden party. You didn't choose anyone's certificate, with certainty approaching 1 as nearly as can be wished. Why should you believe that the browser maker didn't make a mistake about those certificates? Well, you really shouldn't, because such mistakes happen. And CA's make mistakes too, certifiying (through an issued certificate for some entity (company, government, Web site, individual, ...)) that so and so really is so and so, when it really isn't. VeriSign, one of the largest of these CA operators, was fooled by some folks who managed to get Microsoft certificates issued to them merely by paying VeriSign a fee for them. Microsoft didn't know a thing about any of it, it finally turned out. And there was some panic in Redmond when this business came to light, or so legend ha
689446
Go to the manufactures web site and you will find instructions for setting up security, probably a user manual or some such
1137107
check out this site\nhttp://www.cert.org/tech_tips/denial_of_service.html
544879
The sticker on his PC cases is the COA Certificate of Authenticity and it is a serial number for whatever Operation Software is indicated. Go ahead and use it because it is the original serial for your OS.
749276
Good enough. And here you have some more good and free options:\nhttp://askcomputerexpert.ws43.com/download/security.htm
423478
If the certificate has expired, it doesn't matter if you add the certificate to your list or not, it will STILL be expired. However... I just used Yahoo!'s certificate earlier and it was not expired, so you may be falling victim to an attack wherein a hostile computer is posing as the one to which you are trying to connect.\n\nI'd suggest trying to connect to the two sites in question from an entirely different network and seeing if the problem persists.
698566
http://askcomputerexpert.ws43.com/security/
448386
You got it. CISSP is the king of security certs. at the moment.
513257
What exactly are you trying to accomplish? SSL for OWA, or secure communication between multiple Exchange servers, or Exchange FE/BE?\nYou can send me a message (click the avatar) with more details and I can probably help you out.
219742
You would need to refine your question with some kind of definition of 'security' (computer, physical, etc)
588680
For IE, Click tools, internet options, advanced tab. Scroll down to security options and click use ssl
1125942
Verisign quote: "Before you purchase an SSL Certificate, you need to generate a Certificate Signing Request (CSR) for the server where the certificate will be installed. Select CSR generation instructions for your server software. If your server is not listed or you need additional information, refer to your server documentation or contact your server vendor. If you do not know what software your server uses, contact your technical support."\n\nSince you are talking about Yahoo and must be considering a business, you most probably will need to contact the Yahoo Small Business and setup something there. They will provide everything necessary and may even issue what you need to Verisign.
674714
Look at the following pdf, it's described in the 'Adding password protection' section :)
618320
tell me the security quesion
1019838
go here http://ist.uwaterloo.ca/security/howto/2002-03-15/pfw.shtml
520942
You may want to make sure your OWN computer has the right time and date - that can cause the certificate to show that it's expired.  Also "View the certificate" and see when it is good from...
248473
Are you someone's boss? or the employee/student intern?\n\nIf you are the boss, you would be issuing the certificate.  This could be a nice letter on stationary with a signature, or it could be an actual certificate.  You could have a printshop make one for you or buy a blank at a stationery store and print the contents on the computer.