Tasks: Write the following protocols (Using the notions given in the lectures)
Protocol 3: A and B both have their own un-certi?ed public key, respectively. Write a key transport protocol for them to establish a session key. Analyse potential attacks and give a method of prevention. Implement it using Pari/GP. Provide the PG script and a screen shot in submission. The example of RSA PG program is provided in Moodle. Download Pari/GP: https://pari.math.u-bordeaux.fr
Protocol 5: A and B want to have a private "handshake". Upon a handshake, both know that they are communicating with an authorised party but the identity of its partner is not revealed. Let assume that both A and B come from an organisation and hold a signed public key by the organisation. Let us say: A's public key is yA = ga mod p and B0s pubic key is yB = gb mod p, where p is a safe prime, g is a generator of Z∗ p, a ∈ ZP is the identity of A and b ∈ ZP is the identity of B. Further, we assume that SA is the signature on yA signed by the organisation and SB is the signature on yB signed by the organisation. Write a concrete private handshake by using a zero-knowledge proof technique.
Protocol 7: There are three mobile service domains; each has an authentication server. We denote by AS1, AS2, and AS3 the corresponding authentication servers. For simplicity, let AS1 AS2, and AS3 represent those three domains. This mobile system can provide mobile communication services to a large number of users. For simplicity, we assume that two mobile users (A and B) are currently in the system only, where A has registered with AS1 and B has registered with AS2. They, therefore, call their registering domain home (therefore, share a long term secret key with their home). Both A and B are mobile, in the sense that they can move to any existing domains and they want to communicate securely and anonymously wherever they are located. In this task, you consider the case where A has travelled to AS2 and B has travelled to AS3. Write an authenticated key establishment protocol for A and B to establish a session key.
Security Requirements:
- Authenticity: All parties involved in the communication must be authenticated by related communication partners.
- Con?dentiality: All information must be protected against eavesdropping.
- Anonymity: User ID must be protected against outsiders.
- Freshness: All messages must be fresh and secure against reply attacks.
- Integrity: Integrity protection should be applied to all communication flows.