1. Digital Signatures A Brief Overview by Tim Sigmon August, 2000

2. Digital Signatures u Legal concept of “signature” is very broad –any mark made with the intention of authenticating the marked document u Digital signatures are one of many types of electronic signatures u Example electronic signatures –loginid/password, PIN, card/PIN –digitized images of paper signatures –digitally captured signatures (UPS, Sears, etc.) –typed notations, e.g., “/s/ John Smith” –email headers

3. Digital Signatures (cont’d) u “digital signature” means the result of using specific cryptographic processes u Digital signatures operate within a framework of hardware, software, policies, people, and processes called a Public Key Infrastructure (PKI) u Note: PKI also supports other security requirements; in particular, confidentiality, both during transmission (e.g., SSL) and for storage

4. Public Key Cryptography u First, “secret key” or symmetric cryptography –same key used for encryption and decryption –orders of magnitude faster than public key cryptography u Public key technology solves the key exchange problem (no shared secrets!) u Public key and private key that are mathematically linked u Private key not deducible from public key u Confidentiality: one key encrypts, other decrypts u Digital signature: one key signs, other validates

5. Digital Signature example

6. Signed Email example u (show example of sending/receiving digitally signed email using Netscape Messenger) u (uses S/MIME)

7. Problem: relying party needs to verify a digital signature u To do this, must have an assured copy of the signer’s public key –signer’s identity must be assured –integrity of public key must be assured u Potential options for obtaining public keys –signer personally gives their public key to relying party –relying party obtains the desired public key by other “out of band” means that they trust, e.g., transitive relationships, signing parties, etc. u But, what about strangers? what about integrity of the public key?

8. Public Key (or Digital) Certificates u Purpose: validate both the integrity of a public key and the identity of the owner u How: bind identifying attributes to a public key (and therefore to the keyholder of the corresponding private key) u Binding is done (i.e., digitally signed) by a trusted third party (Certification Authority) u It is this third party's credibility that provides "trust"

9. X.509 v3 Certificates u Subject’s/owner’s identifying info (e.g., name) u Subject’s/owner’s public key u Validity dates (not before, not after) u Serial number u Level of assurance u Certification Authority’s name and signature u Extensions

10. Example Certs u (this is where I show and describe the contents of the actual certificates that were used to verify a digitally signed email message)

11. Distribution of Certificates u since certs carry public info and are integrity- protected, they can be distributed and shared by any and all means, e.g., –distribute via floppies or other removable media –publish on web sites –distribute via email (e.g., S/MIME) –directory lookups (e.g., LDAP, X.500) u distribution via directories is the ultimate solution u however, many important applications and uses of digital signatures can be implemented without the implementation or use of sophisticated directories

12. Trust and Certification Paths u Relying party needs an assured copy of the issuing CA’s PK in order to validate a certificate containing the signer’s PK u In general, a chain of multiple certificates that ends at a trusted root may be needed u How to organize the CA’s? –single top-down hierarchy (yikes!) –multiple hierarchies (Netscape/Microsoft disservice) –cross certifications (e.g., Federal BCA, Virginia’s BCA) u Revocation and CRLs (certificate revocation lists)

13. Where are we now? u Technologies are still evolving but are very usable u Policies and legal standing exist but still developing (need case law) –Code of Virginia, Federal law –Uniform Electronic Transctions Act u Browsers/email already contain a lot of capability u Particular uses widely taking place, e.g., SSL u Some universities making more use, e.g., MIT u Federal government taking a leadership role u ITC/UVa project for deployment

14. DS efforts in Virginia u Digital Signature Initiative (COTS workgroup) formed to pursue pilot deployments u UVa led development of a bridge certification architecture (modeled after federal bridge) u Pilot project sponsors –VIPNet, DIT, DGIF –DMV, DOT, DGS –Counties of Chesterfield, Fairfax, Wise –Cities of Norfolk, Charlottesville u http://www.sotech.state.va.us/cots –Virginia’s Council on Technology Services

15. Portals at UVa A Status Report by Tim Sigmon August, 2000

16. Portal Definition u problem: every person/group has a different definition u working definition: deliver information and services in an integrated, customized, and personalized manner u elements that we include: –authenticated access –customization - system presents info that is peculiar to the specific user –personalization - user controls certain aspects –break down organizational views/barriers

17. Background and Players u discussions among ITC, Univ. Relations, Student Council, Student Affairs,.... u JA-SIG conference and uPortal evaluation u development of “e-volving University” proposal u Reynolds and Sweeney presentation to Senior Cabinet u team is led by Nancy Tramontin and Debbie Mills

18. First Phase u deliver first version of student portal by Jan., 2001 u will not use uPortal (nor any other portal framework) u desired functionality –authenticated access (using existing passwords) –brief email stats and web-based email access –calendar that includes student events (not personal, yet) –course links –personal links (i.e., bookmarks) –personal reminders (?) –news, announcements, weather –important “fixed” links