Abstract
One of the main challenges of securing effective computation in diverse network devices tends to be a limitation of their computational power. Server assisted signature scheme was recently presented as nonrepudiation service for mobile and constrained devices. They all tend to have a feature in common: limited computational capabilities and equally limited power (as most operate on batteries). The scheme suffered with high storage requirements and memory requirements for the mobile clients. This makes them ill-suited for public key signatures. This paper examines practical and conceptual implications of using Server-Aided Signatures (SAS) for these devices. SAS is a signature method that relies on partially-trusted servers for generating (normally expensive) public key signatures for regular users. Although the primary goal is to aid small, resource- limited devices in signature generation, SAS also fast certificate revocation, signature causality and with reliable timestamping.
 Keywords: Public key infrastructure; Digital signature; Certificate authority.
Highlights
Digital signature schemes are among the most fundamental and useful inventions of modern cryptography
Setup initializes the settings for Security Mediators (SEMs) and regular users; Sign computes SAS signatures on given messages, which can later be validated by running Verify
In case of a mismatch, SEM replies to Ui with the half-signature produced in the last protocol run and aborts. (Note that SEM keeps a record of all previously generated half-signatures) SEM proceeds to verify the received k-th “private” key (SKki ) with Ui's root public key in Certi
Summary
Digital signature schemes are among the most fundamental and useful inventions of modern cryptography In such schemes, each user generates a (private) signing key and a (public) verification key. While digital signatures are rapidly becoming ubiquitous, one of the major recent trends in computing has been towards so-called smart devices, such as PDAs, cell phones and sensors These devices come in many shapes and sizes and are used for a variety of purposes, they tend to have a feature in common: limited computational capabilities and limited power (as most operate on batteries). Ÿ SEM checks Alice's certificate validity and, if not revoked, computes a half-signature over the data as well as other parameters (including the one-time token). Verifying a SAS signature is easy: after obtaining the signature, verifier (Bob) first verifies the correctness of SEM's public key signature, checks the link between two halves i.e. verifies user's (Alice's) one-time signature
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Technology and Management Research
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
