Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Sat, 6 Apr 2013 13:42:15 -0700 (PDT)
From: deepika dutta <>
To: "" <>
Subject: des-bs-doubt


I want to know the reason behind using the following representation of key and plaintext in bitsliced des.

For plaintext: Swapping the 32 bit halves before doing encryption though in the DES standard these halves are swapped after the last round.

For key: Storing the 7 bits per byte in little endian form in DES_bs_all.K

Is there any performance issue in this? If I want to swap the plaintext after last round and store the 7 bits per byte in big endian form in DES_bs_all.K, then will there be any problem in this representation? (of course I would have to change the indexes of B and K referred in sbox functions).  


Content of type "text/html" skipped

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.