Talk:Key clustering
| This article is rated Stub-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||
| ||||||||||||||||||
Equivalent keys vs key clustering
Is key clustering exactly the same as equivalent keys? The article is not clear enough whether "clustered keys" in the presence of different plaintexts must also produce the same ciphertexts or not. -- intgr [talk] 11:47, 20 July 2017 (UTC)
- No, key clustering is very different from the issue of equivalent keys. It's an issue having to do with hash tables; namely, that if the hash of two keys are the same, then the values must basically be stored in old-fashioned lists, which causes hash table lookup times to increase. (I'll get rid of the misleading WikiProject Cryptography header and replace it with a WikiProject Computer Science one.) Duckmather (talk) 20:44, 3 June 2021 (UTC)
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.