DOC PREVIEW
PSU CSE 543 - Infrastructure

This preview shows page 1-2-19-20 out of 20 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 20 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 20 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 20 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 20 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 20 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

CSE543 Computer (and Network) Security - Fall 2007 - Professor JaegerCSE 543 - Computer SecurityLecture 8 - PKISeptember 20, 2007URL: http://www.cse.psu.edu/~tjaeger/cse543-f07/CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page Meeting Someone New•Anywhere in the Internet2CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page Public Key Infrastructure•System to “securely distribute public keys”–Q: Why is that hard?•Terminology:–Alice signs a certificate for Bob’s name and key•Alice is issuer, and Bob is subject–Alice wants to find a path to Bob’s key•Alice is verifier,and Bob is target–Anything that has a public key is a principal–Anything trusted to sign certificates is a trust anchor•Its certificate is a root certificate3CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page What is a certificate?•A certificate …–… makes an association between a user identity/job/attribute and a private key–… contains public key information {e,n}–… has a validity period–… is signed by some certificate authority (CA)•Issued by CA for some purpose–Verisign is in the business of issuing certificates–People trust Verisign to vet identity 4CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page Why do I trust the certificate?•A collections of “root” CA certificates–… baked into your browser–… vetted by the browser manufacturer–… supposedly closely guarded (yeah, right)•Root certificates used to validate certificate–Vouches for certificate’s authenticityCA(signs)CertificateSignature5CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page What is a PKI?•Rooted tree of CAs•Cascading issuance–Any CA can issue cert–CAs issue certs for children… … …RootCA1CA2 CA3CA11 CA12 CA21 CA22CA1nCert11a Cert11b Cert11c… … … …6CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page Certificate Validation… … …RootCA1CA2 CA3CA11 CA12 CA21 CA22CA1nCert11a Cert11b Cert11c… … … …CertificateSignature7CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page PKI and Revocation•Certificate may be revoked before expiration–Lost private key–Compromised –Owner no longer authorized •Revocation is hard …–The “anti-matter” problem–Verifiers need to check revocation state•Loses the advantage of off-line verification–Revocation state must be authenticated8CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page Trust•What is trust?–Is the belief that someone or something will behave as expected or in your best interest?–Is is constant?–Is is transferable?–Is it transitive?–Is is reflexive?9CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page 10 Risks of PKI•This is an overview of one of many perspectives of PKI technologies–PKI was, like many security technologies, claimed to be a panacea –It was intended to solve a very hard problem: build trust on a global level–Running a CA -- “license to print money”•Basic premise:–Assertion #1 - e-commerce does not need PKI–Assertion #2 - PKI needs e-commerce•Really talking about a full PKI (everyone has certs.)10CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page Risk 1 - Who do we trust, and for what?•Argument: CA is not inherently trustworthy–Why do/should you trust a CA?–In reality, they defer all legal liability for running a bad CA–Risk in the hands of the certificate holder•Counter-Argument: Incentives–Any CA caught misbehaving is going to be out of business tomorrow –This scenario is much worse than getting sued–Risk held by everybody, which is what you want•Everyone has reason to be diligent11CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page Risk 2 - Who is using my key?•Argument: key is basically insecure–Your key is vulnerable, deal with it–In some places, you are being held responsible after a compromise•Counter-Argument: this is the price of technology–You have to accept some responsibility in order to get benefit–Will encourage people to use only safe technology•Q: what would happen is same law applied to VISA?12CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page Risk 3 - How secure is the verif(ier)?•Argument: the things that verify your credential are fundamentally vulnerable–Everything is based on the legitimacy of the verifier root public key–Browsers transparently use certificates•Counter-Argument: this is the price of technology–You have to accept some risk in order to get benefit–Will encourage people to use only safe technology•Q: What’s in your browser?13CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page Risk 4 - Which John Robinson is he?•Argument: identity in PKI is really too loosely defined–No standards for getting credential –No publicly known unqiue identifiers for people–So, how do you tell people apart–Think about Microsoft certificate•Counter-Argument: due diligence–Only use certificates in well known circumstances–When in doubt, use other channels to help•Q: Is this true of other valued items (checks?)14CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page Risk 5 - Is the CA an authority?•Argument: there are things in certificates that claim authenticity and authorization of which they have no dominion–“rights” (such as the right to perform SSL) - this confuses authorization authority with authentication authority–DNS, attributes -- the CA is no the arbiter of these things•Counter-Argument: this is OK, because it is part of the implicit charge we give our CA -- we implicitly accept the CA as authority in several domains15CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page Risks 6 and 7•6 : Is the user part of the design?–Argument: too many things hidden in use, user has no ability to affect or see what is going on–Counter-Argument: Users would screw it up anyway, too sophisticated•7 : Was it one CA or CA+RA?–Argument: separation of registration from issuance allows forgery–Counter-Argument: this is an artifact of organization, only a problem when CA is bad (in which case you are doomed anyway) 16CSE543 Computer (and Network) Security - Fall 2007 - Professor Jaeger Page Risks 8 and 9•8 : How


View Full Document

PSU CSE 543 - Infrastructure

Documents in this Course
Agenda

Agenda

14 pages

HYDRA

HYDRA

11 pages

PRIMA

PRIMA

15 pages

CLIMATE

CLIMATE

15 pages

Load more
Download Infrastructure
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Infrastructure and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Infrastructure 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?