An advanced certificate validation service and architecture based on XKMS

Abstract

The appearance of some laws that make the electronic signature (e‐signature) legally equivalent to the handwritten signature (under some circumstances) has favoured its use in different fields, such as e‐commerce and e‐government. In these fields, the e‐signatures associated to some documents have to remain valid over long periods of time. For these kinds of e‐signatures, Advanced Electronic Signature (AdES) forms have appeared. These forms specify the information to include along with the e‐signature so that it remains valid for a long time after its creation. Basically, this information comprises signers' certificates, a set of certificates up to a trust anchor, certificate validation responses, etc. These data can be gathered by using different Public Key Infrastructure‐compliant protocols. However, the support of different protocols is complex for clients. XML Key Management Specification (XKMS) appeared with the aim of simplifying the certificate management, but it only supports a simple validation mechanism that does not provide the information needed for long‐term validation. As a solution to this problem, we have extended XKMS by defining an advanced certificate validation service to support the obtaining of validation data needed for different scenarios, such as the building of AdES forms or validation data registries. This extension also defines the different components needed to support this kind of a service. Furthermore, the defined service has been implemented and incorporated into an e‐government infrastructure. Copyright © 2010 John Wiley & Sons, Ltd.

SIPmsign: a lightweight mobile signature service based on the Session Initiation Protocol

“…As there are several possibilities, we do not indicate the messages that will be exchanged, and these are only shown as step 0a in Figure . Furthermore, the PKI offers some certificate validation mechanisms such as Certificate Revocation Lists (CRLs), Online Certificate Status Protocol (OCSP), XKMS, Advanced Electronic Signatures (AdES), and Certificate Validation Service (CVS) .…”

“…If the MASP correctly verifies the m‐signature, then the access to the application/services is provided or the transaction continues. For the validation of the certificate associated to the signature or in the event MASP has to store the m‐signature during long periods of time, the use of AdES CVS is recommended for obtaining validation information as well as the various evidences required for its storage during long periods.…”

A lightweight payment scheme for real-time services based on SIP

“…These proposals, which are designed to make the payment in SIP are [6][7][8][9]12]. From these proposals we can point out that [5,6,8,9,11] are not suitable for making micropayments since a third party participates in each payment and asymmetric cryptography is used, which also involves certificates, verifications [53] and increased transactions costs [13]. Therefore, they are not suitable for making real-time micropayments.…”