- Add @ to swapkey, to disable it in classification

- Modify key Compromise for protocols that contain a timestamp to make the
  key compromise disclose a timestamp with a different type, namely 
  ExpiredTimeStamp so that they will not be accepted as timestamps in a new
  session, thereby simulating that they are expired.
This commit is contained in:
gijs
2005-08-12 11:55:24 +00:00
parent 149b774b18
commit 44bc36edc5
9 changed files with 24 additions and 17 deletions

View File

@@ -11,7 +11,8 @@
# According to SPORE there are no attacks on this protocol, scyther
# finds one however. This has to be investigated further.
usertype Server, SessionKey, GeneralizedTimestamp, TicketKey;
usertype Server, SessionKey, TimeStamp, TicketKey;
usertype ExpiredTimeStamp;
secret k: Function;
const a, b, e: Agent;
@@ -33,7 +34,7 @@ protocol kslLoweSessionKeyCompromise(C)
const Ni,Nr,Nc,Ma,Mb: Nonce;
const Kir: SessionKey;
const Kbb: TicketKey;
const Tr: GeneralizedTimestamp;
const Tr: ExpiredTimeStamp;
var I,R,S: Agent;
read_C1(C,C, I,R,S);
@@ -82,7 +83,7 @@ protocol kslLowe(A,B,S)
const Nb,Nc,Mb: Nonce;
var Kab: SessionKey;
const Kbb: TicketKey;
const Tb: GeneralizedTimestamp;
const Tb: TimeStamp;
var T: Ticket;
read_1(A,B, Na, A);