Secure and Fast Encryption Routine: Difference between revisions

Content deleted Content added
H3llBot (talk | contribs)
m BOT: Checking dead links; Marked 1 link with {{Dead link}} (Further info: WP:DEADLINK)
H3llBot (talk | contribs)
m BOT: Checking dead links; Added 1 archived Wayback link, Removed 1 {{Dead link}} template
Line 11:
There are two more-recent members of the SAFER family that have made changes to the main encryption routine, designed by the Armenian cryptographers Gurgen Khachatrian and Melsik Kuregian in conjunction with Massey.
 
* '''SAFER+''' (Massey et al., 1998) was submitted as a candidate for the [[AES process|Advanced Encryption Standard]] and has a block size of 128 bits. The cipher was not selected as a finalist. [[Bluetooth]] uses custom algorithms based on SAFER+ for key derivation (called E21 and E22) and authentication as [[message authentication code]]s (called E1). Encryption in Bluetooth does not use SAFER+.<ref name="bt-preliminary">{{cite paper |author=Sil Janssens |date=2005-01-09 |title=Preliminary study: Bluetooth Security |url=http://student.vub.ac.be/~sijansse/2e%20lic/BT/Voorstudie/PreliminaryStudy.pdf |accessdate=2007-02-27 }} {{Dead link|datearchiveurl =November 2010http://web.archive.org/web/20070213182910/http://student.vub.ac.be/~sijansse/2e+lic/BT/Voorstudie/PreliminaryStudy.pdf |botarchivedate =H3llBot 2007-02-13}}</ref>
* '''SAFER++''' (Massey et al., 2000) was submitted to the [[NESSIE]] project in two versions, one with 64 bits, and the other with 128 bits.