The final step of the digital signing is to put all the pieces together and protect the combination of files and identity certificate with the private key which only the user can control.
The result of this action is a string of numbers and characters. This string is stored again in our signature XML file. In the example below, it’s on row 21, in the element called SignatureValue.
Since the private key is inside your mobile phone, this is where the signature value is created also.
The final step is to make the whole thing deliverable. For this reason, an ASiC container was invented, which puts together the signed files and signature XML files.
ASiC container file is actually a .zip file. For example, if you just rename the extension .asic to .zip you can unzip it and you get direct access to original files and the signature.xml files.
In case there are multiple signers, you fill find multiple signature.xml files in the unzipped container.
.ID signatures combine a myriad of security technologies to ensure that once the signature is associated with the digital file it is very hard to dispute that the signature is either not for this file, nor associated with this person, nor authorised by this person. In short, these signatures are as secure as they can potentially be in the digital world.
To achieve this we create immutable digital fingerprints from the signed files, issue digital identity certificates, bind the certificates with public-private keys, keep those keys securely on your mobile device and combine all those together in secure container.