English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

We revisit the traditional framework of wireless secret key generation, wheretwo parties leverage the wireless channel randomness to establish a secret key.The essence in the framework is to quantify channel randomness into bitsequences for key generation. Conducting randomness tests on such bit sequenceshas been a common practice to provide the confidence to validate whether theyare random. Interestingly, despite different settings in the tests, existingstudies interpret the results the same: passing tests means that the bitsequences are indeed random.  In this paper, we investigate how to properly test the wireless channelrandomness to ensure enough security strength and key generation efficiency. Inparticular, we define an adversary model that leverages the imperfectrandomness of the wireless channel to search the generated key, and create aguideline to set up randomness testing and privacy amplification to eliminatesecurity loss and achieve efficient key generation rate. We use theoreticalanalysis and comprehensive experiments to reveal that common practice misusesrandomness testing and privacy amplification: (i) no security insurance of keystrength, (ii) low efficiency of key generation rate. After revision by ourguideline, security loss can be eliminated and key generation rate can beincreased significantly.

How to Test the Randomness from the Wireless Channel for Security?