Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Communications Encryption Privacy Security News

Chapel Hill Computational Linguists Crack Skype Calls 156

mikejuk writes "You might think of linguistics as being interesting but not really useful. Now computational linguistics [PDF of original paper] has been used to crack Skype encryption and reconstruct what is being said in a VoIP call. What is surprising is that though they are encrypted, the frames that make up a Skype call contain clues about what phonemes are being spoken."
This discussion has been archived. No new comments can be posted.

Chapel Hill Computational Linguists Crack Skype Calls

Comments Filter:
  • Side channel attack (Score:5, Informative)

    by betterunixthanunix ( 980855 ) on Thursday May 26, 2011 @04:25PM (#36255566)
    The wording in TFS is a little misleading; they did not "crack Skype encryption," they found an exploitable side channel in Skype. The crypto itself has not been cracked, but it was being used in a way that leaked lots of information.
  • Encrypting a wave (Score:2, Informative)

    by Anonymous Coward on Thursday May 26, 2011 @04:33PM (#36255692)

    Of course, since the data basically represents sound waves, there is a certain level of predictability and pattern on the data unlike normal data which is much more random.

    It would have to be a special encryption to get rid of this pattern using a more dynamic algorithm that changes as it progress (which can make it annoying to decrypt or simpler to detect) or disjoint the data over a greater amount of data (making it somewhat harder to find the patterns though still might be possible) of the encryption though that is difficult in a time sensitive app like Skype which encrypts and sends as it receives the data.

  • by subreality ( 157447 ) on Thursday May 26, 2011 @04:56PM (#36256020)

    The reason why is that any serious encryption attempt of IP traffic would make all packets a constant size, significantly below expected MTU size (taking into account tunnels). This attack would not exist in that scenario.

    It's actually harder than that. You also have to generate the packets at an even rate as well, or you'll still have some leakage.

    Even after you do that, the presence or absence of a stream of packets will at the very least indicate if a call is in progress; to defend against that, you have to *always* transmit the stream.

    Even then you're leaking information about the maximum amount of data you could be communicating.

    The goalposts keep moving right on down the field when you're talking about side channels. You just have to pick the point where you're comfortable.

  • by NoSig ( 1919688 ) on Thursday May 26, 2011 @05:57PM (#36256774)
    If the padding is random you'll decrease the amount of information leaked, but there may still be enough information leaked to reconstruct some conversations. What you really need for total security from this attack is to eliminate the side-channel completely, such as by sending packets of the same size and with the same frequency no matter how much data you've actually got that needs sending. That is a form of padding too, but it is better than random.

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?

Working...