Known Key Secrecy Secrecy of session key Ku Sample Clauses

Known Key Secrecy Secrecy of session key Ku. In our solution, it is hard to disclose the shared session key Ku=h(IDi||Kpub) for the following reasons: ─ Each node gets the public parameter Kpub from the legal CSA to construct a valid session key. Moreover, there is no exchange of information IDi before establishing the key. So, the attacker cannot guess nodes of the current communication. ─ Ku is hashed with one-way hash function. Therefore, no information can be xxxxx- dropped from the session key. Our proposed scheme achieves the known key secrecy property. Secrecy of session key “key” In the proposed scheme, a session key “key” can be deployed only after mutual au- thentication between SEi and SEj. Therefore, an adversary cannot succeed communi- cation with legitimate node in the network without passing the fog. Indeed, to over- come this process, an attacker must have allowable IDi, a secret variable and a vali- dated Authenticated key . Therefore, the attacker cannot construct a valid session key since each node generates these parameters secretly on its side. In addition, the attacker needs to pass through the semi-trusted fog server while executing the algo- rithm. So, the session key is secured, and it is too hard to steal it.