25.01.2014 Views

Fulltext - International Journal of Computer Technology and ...

Fulltext - International Journal of Computer Technology and ...

Fulltext - International Journal of Computer Technology and ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

which means that the Sender <strong>and</strong> the Receiver provide all<br />

the transcripts <strong>of</strong> the message in the deniable authentication<br />

protocol to them.<br />

If DAP satisfies the condition one <strong>and</strong> four in:<br />

Inj-event (whole sender (Receiver, x)) = inj-event(whole Receiver (Sender, x) )<br />

Inj-event (whole Thirdparty (Receiver, x)) = inj-event(whole Thirdparty (Sender, x) )<br />

Definition DAP <strong>and</strong> DAP’ satisfies the correspondence <strong>and</strong><br />

with public variables V = φ, then DAP is a secure deniable<br />

authentication protocol with session in a adversary model in<br />

strong deniability. In the above definition <strong>of</strong> DAP the<br />

injective correspondence can be instead by non-injective<br />

correspondence.<br />

Weak deniability:<br />

The purpose <strong>of</strong> weak deniability is to protect the privacy <strong>of</strong><br />

Sender. After execution <strong>of</strong> the deniable authentication<br />

protocol the Receiver can prove to have spoken to Sender<br />

but not the content <strong>of</strong> what the Sender authenticated in a<br />

way that the Receiver cannot convince a third party.<br />

Deniable Authentication Protocol<br />

Security Properties<br />

Active Adversary Model<br />

Sanjay Kumar Sonkar et al ,Int.J.<strong>Computer</strong> <strong>Technology</strong> & Applications,Vol 3 (2), 525-531<br />

Relating the Two Models:<br />

Meng & Shao<br />

Mechnized Model<br />

Automated<br />

Verification<br />

ISSN:2229-6093<br />

In order to prove any relationship between the formal <strong>and</strong><br />

computational worlds, we need to define the interpretation<br />

<strong>of</strong> expressions [8] <strong>and</strong> patterns. Once an encryption scheme<br />

is depicted, we can define the interpretation function α,<br />

which assigns to each expression or pattern M a family <strong>of</strong><br />

r<strong>and</strong>om variables {α η (M)} η∈ N such that each α η (M) takes<br />

values in strings. For expressions:<br />

Blocks are interpreted as strings,<br />

Each key is interpreted by running the key<br />

generation algorithm,<br />

Pairs are translated into computational pairs,<br />

Formal encryptions terms are interpreted by<br />

running the encryption algorithm.<br />

Difference between Formal approach <strong>and</strong><br />

Computational approach [15]:<br />

Formal approach Computational<br />

approach<br />

Message Terms Bits-strings<br />

Encryption Idealized Algorithm<br />

Adversary Idealized Any polynomial<br />

algorithm<br />

Secrecy Reach ability-based Indistingability<br />

property property<br />

Guarantees Unclear Strong<br />

Pro<strong>of</strong> Automatic By h<strong>and</strong> <strong>and</strong> errorprone<br />

Balnchet Calculus<br />

Computational Model<br />

Crypto Verification<br />

Figure 2: Model <strong>of</strong> automatic verification <strong>of</strong> deniable authentication<br />

protocols<br />

If the Receiver want to prove that the Sender have<br />

authenticated messages to Receiver, he must provide the<br />

evidence related to the thing. An adversary model in weak<br />

deniability: When discussing the weak deniability, in<br />

addition the adversary has the ability in previous section; we<br />

always suppose that only the Receiver generates the<br />

evidence that the Sender have authenticated messages to<br />

Receiver. Receiver cannot get the secret information <strong>of</strong> the<br />

Sender, for example the private key <strong>of</strong> Sender. Receiver can<br />

provide his secret information to the Third party.<br />

If DAP’ satisfies the condition one in definition DAP <strong>and</strong><br />

DAP’ satisfies the correspondence:<br />

Inj-event (whole sender (Receiver, x)) = inj-event(whole Receiver (Sender, x) )<br />

Inj-event (whole Thirdparty (Receiver, x)) = inj-event(whole Thirdparty (Sender, x) )<br />

<strong>and</strong> with public variables V = φ, then DAP is a secure<br />

deniable authentication protocol with session functions in a<br />

adversary model in weak deniability. In the above definition<br />

<strong>of</strong> DAP the injective correspondence can be instead by noninjective<br />

correspondence.<br />

Our Contribution:<br />

The primary contribution <strong>of</strong> this paper is that it tried to bring<br />

about various concepts which are requisite for concrete<br />

development in pro<strong>of</strong>s <strong>of</strong> cryptography protocols <strong>and</strong><br />

remove the bottleneck reason for its failure. In particular, we<br />

define the equivalence between formal messages in the<br />

presence <strong>of</strong> both key cycles <strong>and</strong> secret shares, <strong>and</strong> then<br />

prove the computational soundness [13][16] about formal<br />

encryption in this setting.<br />

1. First computational analysis <strong>of</strong> an industrial protocol:<br />

Consider authentication[29] <strong>and</strong> secrecy<br />

properties[26],<br />

Analyzed Basic Kerberos 5 <strong>and</strong> public-key<br />

Kerberos[22],<br />

Kerberos is complex (e.g. PKINIT uses both<br />

public-key <strong>and</strong> symmetric).<br />

Cryptographic primitives (Encryption, Signatures,<br />

MACs).<br />

2. Pro<strong>of</strong>s were carried out symbolically in the BPW<br />

model:<br />

Pro<strong>of</strong>s in Dolev-Yao style model are<br />

cryptographically sound,<br />

Pro<strong>of</strong>s can be automated.<br />

528

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!