To hide SIP headers, there are ways like TLS, SIP/MIME (encapsulation). May be you would like to use TLS in this particular case, which will prevent any attacker to generate accurate UPDATE message.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of radhakrishna Sent: Wednesday, July 14, 2010 14:01 To: [email protected] Subject: [Sip-implementors] How sip stack can recover from the followingerror condition..... Dear All, I want to know if there is any way to come out of the following problem. UAC UAS ----------------------------INV (CSEQ: 1) ------------------------> <---------------------------200 OK---------------------------------- ----------------------------ACK ------------------------------------> Attacker ----------------Update (CSEQ: 10000) ----------> <------------------- 401/407 ------------------------------ -----------------------UPDATE (CSEQ: 2) ------------------> <----------------------- 500 -------------------------------------- Now since the actual UAC is not aware of the attacker, he will keep incrementing the CSEQ every time and will try to send the request. The request would be successful only after trying for some 9999 times. How do we overcome this kind of situation? We suggest that RFC should have a way to convey the CSEQ value stored by UAS in 500 response message so that UAC can come out of the loop. Can anyone please share your opinion on this issue? Regards, RadhaKrishna _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
