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

Public key authentication (PKA) has been deployed in various services toprovide stronger authentication to users. In PKA, a user manages private keyson her devices called authenticators, and services bind the correspondingpublic keys to her account. To protect private keys, a user uses authenticatorswhich never export private keys outside. On the other hand, a user regularlyuses multiple authenticators like PCs and smartphones. She replaces some of herauthenticators according to their lifecycle, such as purchasing new devices andlosing devices. It is a burden for a user to register, update and revoke publickeys in many services every time she registers new accounts with services andreplaces some of her authenticators. To ease the burden, we propose a mechanismwhere users and services manage public keys based on the owner ofauthenticators and users can access services with PKA using any of theirauthenticators. We introduce a key pair called an Ownership Verification Key(OVK), which consists of the private key (OVSK) and the corresponding publickey (OVPK). All authenticators owned by a user derive the same OVSK from thepre-shared secret called the seed. Services verify the ownership of theauthenticators using the corresponding OVPK to determine whether binding therequested public key to her account. To protect user privacy while maintainingconvenience, authenticators generate a different OVK for each service from theseed independently. We demonstrate the feasibility through the Proof of Conceptimplementation, show that our proposed mechanism achieves some security goals,and discuss how the mechanism mitigates threats not completely handled.

Key Management Based on Ownership of Multiple Authenticators in Public Key Authentication