Recent developments in group key exchange

35
1 Recent developments in group key exchange Mike Burmester Information Security Summer School 200 Florida State University

description

Recent developments in group key exchange. Mike Burmester Information Security Summer School 2005 Florida State University. Outline. 1 . Secure Communication 2. Key Distribution the Diffie-Hellman protocol variants, attacks authentication conference protocols - PowerPoint PPT Presentation

Transcript of Recent developments in group key exchange

Page 1: Recent developments in group key exchange

1

Recent developments in

group key exchange

Mike Burmester

Information Security Summer School 2005Florida State University

Page 2: Recent developments in group key exchange

2

Outline 1. Secure Communication2. Key Distribution the Diffie-Hellman protocol

variants, attacks authentication conference protocols

3. Public Key Certificates trust-graphs hierarchical vs horizontal structures security

4. Conclusion

Page 3: Recent developments in group key exchange

3

1. Secure Communication

Sender(Alice)

Receiver(Bob)

message

Adversary

Security issues

• authenticity• denial of service, etc.

• privacy

Page 4: Recent developments in group key exchange

4

Symmetric keys (privacy)

Alice Bob

E D

private channel

SK SK

Security issue• How to distribute the secret key SK

plaintext ciphertext plaintext

Page 5: Recent developments in group key exchange

5

Public Keys (privacy)

Alice Bob

E D

• It should be hard to compute SKB from PKB

• How do we distribute PKB

plaintext ciphertext plaintext

Security issues

SKBPKB

Authentication channelf

Page 6: Recent developments in group key exchange

6

Public Keys (digital signatures)

Alice Bob

S V

SKA PKA

• It should be hard to compute SKA from PKA

• How to distribute PKA

m m, sigSKA m or

Authentication channel

Security issues

f

Page 7: Recent developments in group key exchange

7

2. Key Exchange protocols the Diffie-Hellman protocol

Zp = {0,1,…,p-1}, p prime, g a generator of Zp*

Alice Bobgsa mod p

gsb mod p

Bob’s Public Key gsb: 0 < sa< p-1, private key sb

Alice’s Public Key gsa: 0 < sa< p-1, private key sa

Key Exchanged: SK = gsasb mod p

Page 8: Recent developments in group key exchange

8

Freshness of keys

If the same key is used many times then the security of the system may be undermined.

It should be hard to compute SK from PK.

Security

Page 9: Recent developments in group key exchange

9

What if 3 or more parties want to sha re a common secret key?

A

C

ED

B

F

K/SKAB

K/SKBD

1. Use DH to get: SKAB , SKBD , SKBE , SKAC , SKCF .

2. .A selects the secret key K at random from Zp*.

K/SKAC

4. B gets K from K /SKAB and sends K/SKAC to D, etc.

3. .A sends K/SKAB to B and K/SKAC to C.

Page 10: Recent developments in group key exchange

10

Group Key Exchange – contributory schemes

Un-1

Un

U2 U3

U1 Round 1: Use DH

Ui broadcasts zi = gri

Page 11: Recent developments in group key exchange

11

Group Key Exchange

Un-1

Un

U2 U3

U1

Round 1:

Each Ui computes the DH key:

Ki = gri ri+1

Ki2

Kn-1n

K23

Knn-1

Page 12: Recent developments in group key exchange

12

Group Key Exchange

Un-1

Un

U2 U3

U1

Ki2

Kn-1n

K23

Knn-1

Round 1: endGroup Key K = K1K2 … Kn

Where Ki = Ki,i+1

But how????

Page 13: Recent developments in group key exchange

13

Group Key Exchange

Un-1

Un

U2 U3

U1

Ki

Kn

K2

Kn-1

Round 2:

Ui broadcasts xi = Ki/Ki-1

Page 14: Recent developments in group key exchange

14

Group Key Exchange

Un-1

Un

U2 U3

U1

Ki

Kn

K2

Kn-1

Round 2:

Each Ui computes

the key:

K = Ki-1n zi

n-1 zi+1n-2 … zi-2

= Ki-1n

(Ki/Ki-1)n-1(Ki+1/Ki)n-2… (Ki-1/Ki-2)

Page 15: Recent developments in group key exchange

15

Authentication 1

How does Alice know that the “shared” secret key has been distributed to all the parties in the conference?

Page 16: Recent developments in group key exchange

16

Group Key Exchange – authentication

Each Ui authenticates (digitally signs) its

• randomness ri

• its zi and xi

and after checking them authenticates the string: • {Ui}|| {ri} || {zi} || {xi}

Page 17: Recent developments in group key exchange

17

Authentication 2

How can Alice be certain which key is Bob’s public key?

2. They may have mutual friends who know theirpublic keys:

Alice Carol Bob, orAlice Carol . . . Bob

Case 1 establishes an a priori trust relationshipCase 2 establishes an induced trust relationship

1. They may have met earlier and exchanged public keys.

Page 18: Recent developments in group key exchange

18

3. Public Key Certificates

Who is who?

PK CERTIFICATEThe public key of Bob is: 010010010 …..

Signed by a Certifying Authority

A PK Certificate establishes authenticity andprovides a means by which a public key can be stored in partially insecure repositories, or transmitted over insecure channels.

Page 19: Recent developments in group key exchange

19

Trust-graphs

A

C

ED

B

F

CAB

CBD

CAC

Certificates can be used to Model the confidence of a network in its public keys by a directed trust-graph, with vertices the entities and edges the certificates.

CBE CCF

Page 20: Recent developments in group key exchange

20

A priori confidence:This is corroborated by the certificates.

Trust-graphs

Induced confidence:This is established by trust-paths that link the entities in the trust-graph.

Page 21: Recent developments in group key exchange

21

A hierarchical infrastructure

U1 U2U3

U4

CA1CA2

RCA

The public key of U4 is certified by the trust-path: RCA CA2 U4

Page 22: Recent developments in group key exchange

22

Security issues

A hacker can penetrate a CA or its

computer system and forge certificates or

get certificates for unauthorized users.

Page 23: Recent developments in group key exchange

23

Threats

1. Whom should we trust (and for what)?2. Which Bob is it?

3. Organizational (insider) attacks

4. Computer system threats: How secure is the computer system of the Certifying Authority? How secure is the computer system of Bob?

Page 24: Recent developments in group key exchange

24

PGP: an unstructured approach

Pretty Good Privacy is a freeware electronicmail system that uses an unstructuredauthentication framework.Users are free to decide whom they trust.PGP does not specify any specific structure for the trust-graph and for this reason is quite vulnerable.

A A1 . . . An B

Page 25: Recent developments in group key exchange

25

A horizontal approach: multiple connectivity

If the trust-graph is (2k+1)-connected thenthere are 2k+1 vertex disjoint trust-paths which connect any two of its vertices

Page 26: Recent developments in group key exchange

26

A 3-connected trust-graph

A B

Page 27: Recent developments in group key exchange

27

Combining horizontal and hierarchical structures

U1

U2

U3

U4

Page 28: Recent developments in group key exchange

28

Security

A secure authentication infrastructure must be, reliable, robust and survivable.

Reliability deals with faults that occur in a

random manner, and is achieved by replication.

Robustness deals with maliciously inducedfaults.

Page 29: Recent developments in group key exchange

29

Survivability deals with the destruction of parts of the infrastructure.

The destruction may affect the entities (e.g. the CA’s) as well as stored data, and may be malicious.

For survivability, the remaining entities should be able to recover enough of the infrastructure to guarantee secure communication.

Page 30: Recent developments in group key exchange

30

Survivability

Reconstruction of a corrupted trust-graph

Entity A asks all its neighbors for a list of their neighbors,

the neighbors of their neighbors, etc

U1 U2 U3 . . . . . . . . . . . . Un

A

faultyAdversary

Page 31: Recent developments in group key exchange

31

Survivability

Some of the neighbors are under the control of the Adversary and may send fake certificates, relating to other entities, real or bogus.

Is it possible to reconstruct a sufficiently good approximation of the trust-graph?

Problem

Page 32: Recent developments in group key exchange

32

Survivability

AnswerYes, provided that there is a bound on the number of penetrated or destroyed cites, and that the trust-graph is sufficiently connected.

Page 33: Recent developments in group key exchange

33

Reconstructing a corrupted trust-graph

The reconstruction involves several stages.

• Round Robin flooding

• a Halting routine

• a Clean-up routine

Page 34: Recent developments in group key exchange

34

Conclusion

Secure key exchange can be achieved in several ways by using cryptographic mechanisms.

Clearly there is a trade off between the securityrequirements and the complexity.

Page 35: Recent developments in group key exchange

35

Conclusion

If the public keys are authenticated via singletrust paths then the system is vulnerable to anypenetration.

By having several vertex disjoint authenticationpaths linking the entities we get robustness against penetration and survivability.