<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DIGITAL TRUST SCIENCE</title>
	<atom:link href="http://digitaltrustscience.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://digitaltrustscience.com</link>
	<description>Secured Solutions For a Better Digital World</description>
	<lastBuildDate>Thu, 12 Jan 2012 22:06:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Peer entity authentication</title>
		<link>http://digitaltrustscience.com/legislation/peer-entity-authentication/</link>
		<comments>http://digitaltrustscience.com/legislation/peer-entity-authentication/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 22:35:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[legislation]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[exchange]]></category>

		<guid isPermaLink="false">http://digitaltrustscience.com/?p=115</guid>
		<description><![CDATA[<p>Authentication is the provision of assurance of the claimed identity of an entity [ISO/IEC 10181-2]. In order to guaranty the success of an exchange and whether at the origin or at the receiving end of the message, exchanging parties must be authentified before the process is initiated. This allows answering two fundamental questions, often forgotten [...]]]></description>
			<content:encoded><![CDATA[<p>Authentication is the provision of assurance of the claimed identity of an entity [ISO/IEC 10181-2]. In order to guaranty the success of an exchange and whether at the origin or at the receiving end of the message, exchanging parties must be authentified before the process is initiated. This allows answering two fundamental questions, often forgotten in the &#8220;traditional&#8221; electronic exchanges:</p>
<p>1- Is the recipient I&#8217;m about to send this information really the one I think he is?<br />
<em>Peer entity authentication: The corroboration that a peer entity in an association is the one claimed [ISO 7498-2]</em></p>
<p>2- Does this message really comes from the person it says it does?<br />
<em>Data origin authentication: The corroboration that the source of data received is as claimed [ISO 7498-2]</em></p>
<p>We offers you the tools to easily obtain guaranties (with full legal value) on your correspondents&#8217; identity.</p>
<p><strong>Document authentication</strong></p>
<p>To ensure a document authentication, a signature should identify what is signed, making it impracticable to falsify or alter either the signed matter or the signature without detection. Again, the provides easy way to apply your  electronic signature to any content attached to your envelope.</p>
<p>Signer authentication and document authentication are tools used to exclude impersonators and forgers and are essential ingredients of what is often called a &#8221; non-repudiation service&#8221; in the terminology of the information security profession.</p>
]]></content:encoded>
			<wfw:commentRss>http://digitaltrustscience.com/legislation/peer-entity-authentication/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Technical standards</title>
		<link>http://digitaltrustscience.com/legislation/technical-standards/</link>
		<comments>http://digitaltrustscience.com/legislation/technical-standards/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 19:38:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[legislation]]></category>
		<category><![CDATA[legal]]></category>
		<category><![CDATA[standards]]></category>
		<category><![CDATA[Technical]]></category>

		<guid isPermaLink="false">http://digitaltrustscience.com/?p=112</guid>
		<description><![CDATA[<p>The value of a legal evidence is ackwnoledged all the more if it also satisfies criteria of durability and portability. Because of the way the evidences are build (it binds the content and the exchanging parties identities with the event it relates to) and by complying to technology standards, provides you with the insurance that [...]]]></description>
			<content:encoded><![CDATA[<p>The value of a legal evidence is ackwnoledged all the more if it also satisfies criteria of durability and portability. Because of the way the evidences are build (it binds the content and the exchanging parties identities with the event it relates to) and by complying to technology standards, provides you with the insurance that you will always be able to use your evidences in a court, at anytime, independantly from our service !</p>
<p><strong>Below is a list of standards strictly followed :</strong></p>
<p>CEN/ISSS &#8211; European Committee for Standardization/ Information Society Standardization System<br />
CWA 14169 &#8211; Secure Signature-creation devices &#8220;EAL 4+&#8221;<br />
CWA 14170 &#8211; Security requirements for signature creation applications<br />
CWA 14171 &#8211; General guidelines for electronic signature verification<br />
CWA 14365 &#8211; Guide on the Use of Electronic Signatures &#8211; Part 1: Legal and Technical Aspects</p>
<p>NIST &#8211; National Institute of Standards and Technology<br />
FIPS Pub 186: Digital Signature Standard. 19 May 1994.<br />
NIST &#8211; FIPS 140-1 Level 2 and 3 physical protection certification</p>
<p>Request for Comments (RFCs)<br />
Housley, R., Polk, W., Ford, W. and D. Solo, &#8220;Internet X.509 Public Key Infrastructure: Certificate and CRL Profile&#8221;, RFC 3280, April 2002<br />
Housley, R., &#8220;Cryptographic Message Syntax&#8221;, RFC 3852, July 2004<br />
Housley, R., &#8220;Cryptographic Message Syntax (CMS) Algorithms&#8221;, RFC 3370, August 2002<br />
Kaliski, B., &#8220;PKCS #7: Cryptographic Message Syntax, Version 1.5.&#8221;, RFC 2315, March 1998<br />
CCITT. Recommendation X.209: Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1).1988</p>
<p>RSA Security &#8211; Public-Key Cryptography Standards (PKCS)<br />
PKCS #1: RSA Cryptography Standard<br />
PKCS #3: Diffie-Hellman Key Agreement Standard<br />
PKCS #7: Cryptographic Message Syntax Standard<br />
PKCS #10: Certification Request Syntax Standard<br />
PKCS #11: Cryptographic Token Interface Standard</p>
]]></content:encoded>
			<wfw:commentRss>http://digitaltrustscience.com/legislation/technical-standards/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Digital certificate</title>
		<link>http://digitaltrustscience.com/legislation/digital-certificate/</link>
		<comments>http://digitaltrustscience.com/legislation/digital-certificate/#comments</comments>
		<pubDate>Tue, 16 Feb 2010 12:11:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[legislation]]></category>
		<category><![CDATA[Digital certificate]]></category>
		<category><![CDATA[electronic ID card]]></category>
		<category><![CDATA[high]]></category>
		<category><![CDATA[key pair]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[signatures]]></category>

		<guid isPermaLink="false">http://digitaltrustscience.com/?p=101</guid>
		<description><![CDATA[<p>To verify an electronic signature, the verifier must have access to the signer&#8217;s public key and have assurance that it corresponds to the signer&#8217;s private key. However, a public and private key pair has no intrinsic association with any person; it is simply a pair of numbers. Some convincing strategy is necessary to reliably associate [...]]]></description>
			<content:encoded><![CDATA[<p>To verify an electronic signature, the verifier must have access to the signer&#8217;s public key and have assurance that it corresponds to the signer&#8217;s private key. However, a public and private key pair has no intrinsic association with any person; it is simply a pair of numbers. Some convincing strategy is necessary to reliably associate a particular person or entity to the key pair.</p>
<p>To associate a key pair with a prospective signer, a certification authority (using public key infrastructure ) issues a certificate, an electronic record which lists a public key as the &#8220;subject&#8221; of the certificate, and confirms that the prospective signer identified in the certificate holds the corresponding private key.</p>
<p><em>The following figure shows the structure of a digital certificate.</em></p>
<p><img src="https://www.evidencecube.com/_commons/images/x509_certificate_fields.jpg" border="0" alt="" /></p>
<p><em>Different classes of certificates can be purchased that correspond to the level of checks made. There are 4 general classes of certificate:</em></p>
<p><strong><br />
Level 1 certificates: </strong>offer the lowest level of assurances and can be easily acquired. They are individual Certificates, whose validation procedures are based on assurances that the Subscriber&#8217;s distinguished name is unique and unambiguous within the Certification Authority&#8217;s Subdomain and that a certain e-mail address is associated with a public key. They are appropriate for digital signatures, encryption, and access control for non-commercial or low-value transactions where proof of identity is unnecessary.</p>
<p><strong>Level 2 certificates: </strong>require additional personal information to be supplied and offer a medium level of assurances in comparison with the other classes.</p>
<p><strong>Level 3 certificates:</strong> may be used for digital signatures, encryption, and access control, including as proof of identity, in high-value transactions. Class 3 individual Certificates provide assurances of the identity of the Subscriber based on the personal (physical) presence of the Subscriber before a person that confirms the identity of the Subscriber using, at a minimum, a well-recognized form of government-issued identification and one other identification credential.</p>
<p>A 4th class (Qualified certificates), like the ones automatically provided with the  electronic ID card, is used for very high quality signatures.</p>
]]></content:encoded>
			<wfw:commentRss>http://digitaltrustscience.com/legislation/digital-certificate/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Qualified certificate</title>
		<link>http://digitaltrustscience.com/legislation/qualified-certificate/</link>
		<comments>http://digitaltrustscience.com/legislation/qualified-certificate/#comments</comments>
		<pubDate>Tue, 16 Feb 2010 12:02:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[legislation]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[Qualified certificate]]></category>
		<category><![CDATA[signature]]></category>
		<category><![CDATA[verification]]></category>

		<guid isPermaLink="false">http://digitaltrustscience.com/?p=98</guid>
		<description><![CDATA[<p>The requirements for qualified certificates are defined by the european directive 1999/93/EC (annex I, dir.) as follow:</p> <p>1- the indication that the certificate is issued as a qualified certificate;</p> <p>2- the identification of the Certification Authority and the State (European or foreigner) in which it is established;</p> <p>3- the name (or pseudonym) of the signatory, [...]]]></description>
			<content:encoded><![CDATA[<p>The requirements for qualified certificates are defined by the european directive 1999/93/EC (annex I, dir.) as follow:</p>
<p>1- the indication that the certificate is issued as a qualified certificate;</p>
<p>2- the identification of the Certification Authority and the State (European or foreigner) in which it is established;</p>
<p>3- the name (or pseudonym) of the signatory, to identify her/him;</p>
<p>4- signature-verification data which correspond to signature-creation data under the control of the signatory;</p>
<p>5- the indication of the period of validity of the certificate;</p>
<p>6- the identity code of the certificate; and</p>
<p>7- the advanced electronic signature of the certification-service-provider (Certification Authority).</p>
]]></content:encoded>
			<wfw:commentRss>http://digitaltrustscience.com/legislation/qualified-certificate/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Qualified signature</title>
		<link>http://digitaltrustscience.com/legislation/qualified-signature/</link>
		<comments>http://digitaltrustscience.com/legislation/qualified-signature/#comments</comments>
		<pubDate>Tue, 16 Feb 2010 11:40:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[legislation]]></category>
		<category><![CDATA[certificate]]></category>
		<category><![CDATA[identity]]></category>
		<category><![CDATA[Qualified signature]]></category>
		<category><![CDATA[secure]]></category>
		<category><![CDATA[signatory]]></category>

		<guid isPermaLink="false">http://digitaltrustscience.com/?p=96</guid>
		<description><![CDATA[<p>A qualified electronic signature is an advanced electronique signature , based on a qualified certificate and created by a secure-signature-creation device.</p> <p>The European Directive defines the qualified electronic signature as follow:<br /> &#8220;[..] Member States shall ensure that advanced electronic signatures which are based on a qualified certificate and which are created by a secure-signature-creation [...]]]></description>
			<content:encoded><![CDATA[<p>A qualified electronic signature is an advanced electronique signature , based on a qualified certificate and created by a secure-signature-creation device.</p>
<p>The European Directive defines the <strong>qualified electronic signature</strong> as follow:<br />
&#8220;[..] Member States shall ensure that advanced electronic signatures which are based on a qualified certificate and which are created by a secure-signature-creation device:</p>
<p>1- satisfy the legal requirements of a signature in relation to data in electronic form in the same manner as a handwritten signature satisfies those requirements in relation to paper-based data; and</p>
<p>2- are admissible as evidence in legal proceedings. [..]&#8221;</p>
<p>The qualified signature may also contain other elements, such as the provision for a specific attribute of the signatory, there can be a limitation on the scope of use of the certificate, such as stipulation that contracts can only be signed with specific countries such as the United States. Additionally, there can be limits on the value of transactions for which the certificate can be used, such as the ability to sign contracts up to a maximumof $10,000 USD.</p>
<p>This type of digital signature has a strong juridical value. A strong digital signature is very useful for business: you are sure of the identity of the signatory, the content of the text, the confidentiality of your business, and the elements you would have in any eventual legal action. No hacker can read the text, modify it, or take the place of the signatory. The judge can&#8217;t make decisions on the juridical value of this qualified signature: it is fixed by the law and nobody can refute it. This kind of electronic signature has a high value, but it must be used in a correct way and thus the signatory has some duties to perform.</p>
<p><strong>Duties of a qualified electronic signature user</strong></p>
<p><strong>Keeping duty.</strong><br />
The signatory has to keep the smart-card and the other tools necessary for a digital signature safe to avoid unauthorized use. If you don&#8217;t secure your signature tools you are responsible for their unauthorized use!</p>
<p><strong>Information duties.</strong><br />
You have to inform your Certification Authority about the limits of the signature, consisting of its use and/or value limits before the smart-card is given out. You have also to inform your Certification Authority as soon as possible about any loss of value in the digital signature, on every circumstance it depends. Here are a few examples of a loss of value: the signatory was one of your employees and now she is retired, the smart-card was stolen from the strong-box with the pin code, or the signatory society had gone bankrupt. In all these cases, if you don&#8217;t inform the Certification Authority you are responsible for any unauthorized use. There are other good examples of information duties: let&#8217;s say your subordinate can sign contracts for up to $10,000 USD and he has a strong digital signature. You didn&#8217;t indicate this value limit to the Certification Authority, so no limit is written into the qualified certificate. The subordinate signs a contract for more than a million dollars. Can you say this contract is void? No, because you didn&#8217;t inform your Certification Authority and consequently the Certification Authority didn&#8217;t inform its third parties, such as its commercial partners. You can only mitigate your losses with the subordinate, and not with the organization that entered into the contract with you.</p>
<p><strong>Update duties.</strong><br />
No key is safe forever, because technology improves and develops such that a good quality algorithm now becomes a low quality algorithm over time. Moreover every mathematical key can be decrypted in a certain time. The digital signature is safe only during its validity period, which is set much shorter than the time an hacker needs to decrypt it. When the validity period is gone the digital signature is no longer safe and the Certification Authority won&#8217;t warrant it any longer. You have to update your digital signature when the validity period is gone, and this update means the receipt of a completely new key. If you continue to use your strong digital signature after the end of the validity period, it loses its juridical value, effectively becomes a weak electronic signature.</p>
]]></content:encoded>
			<wfw:commentRss>http://digitaltrustscience.com/legislation/qualified-signature/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Digital signature creation</title>
		<link>http://digitaltrustscience.com/legislation/digital-signature-creation/</link>
		<comments>http://digitaltrustscience.com/legislation/digital-signature-creation/#comments</comments>
		<pubDate>Tue, 16 Feb 2010 11:13:12 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[legislation]]></category>
		<category><![CDATA[private key]]></category>

		<guid isPermaLink="false">http://digitaltrustscience.com/?p=93</guid>
		<description><![CDATA[<p>Digital signature creation uses a hash result derived from and unique to both the signed message and a given private key. For the hash result to be secure, there must be only a negligible possibility that the same digital signature could be created by the combination of any other message or private key.</p> <p>Digital signature [...]]]></description>
			<content:encoded><![CDATA[<p>Digital signature creation uses a hash result derived from and unique to both the signed message and a given private key. For the hash result to be secure, there must be only a negligible possibility that the same digital signature could be created by the combination of any other message or private key.</p>
<p><strong>Digital signature verification</strong><br />
Digital signature verification is the process of checking the digital signature by reference to the original message and a given public key, thereby determining whether the digital signature was created for that same message using the private key that corresponds to the referenced public key.</p>
<p><strong>Hash</strong><br />
A hash function is an algorithm which creates a digital representation or &#8220;fingerprint&#8221; in the form of a &#8220;hash value&#8221; or &#8220;hash result&#8221; of a standard length which is usually much smaller than the message but nevertheless substantially unique to it.</p>
<p>Any change to the message invariably produces a different hash result when the same hash function is used. In the case of a secure hash function, sometimes termed a &#8220;one-way hash function,&#8221; it is computationally infeasible to derive the original message from knowledge of its hash value. Hash functions therefore enable the software for creating digital signatures to operate on smaller and predictable amounts of data, while still providing robust evidentiary correlation to the original message content, thereby efficiently providing assurance that there has been no modification of the message since it was digitally signed.</p>
]]></content:encoded>
			<wfw:commentRss>http://digitaltrustscience.com/legislation/digital-signature-creation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Advanced signature</title>
		<link>http://digitaltrustscience.com/legislation/advanced-signature/</link>
		<comments>http://digitaltrustscience.com/legislation/advanced-signature/#comments</comments>
		<pubDate>Tue, 16 Feb 2010 11:00:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[legislation]]></category>
		<category><![CDATA[Advanced]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[Electronic signature]]></category>
		<category><![CDATA[signature]]></category>

		<guid isPermaLink="false">http://digitaltrustscience.com/?p=90</guid>
		<description><![CDATA[<p>The European Directive defines the advanced electronic signature as follow:</p> <p>In order to be considered as advanced electronic signature, a digital signature must be:</p> <p>1- Uniquely linked to the signatory</p> <p>2- Capable of identifying the signatory</p> <p>3- Created using means under the sole control of the signatory</p> <p>4- Linked to the data to which it [...]]]></description>
			<content:encoded><![CDATA[<p><strong>The European Directive defines the advanced electronic signature as follow:</strong></p>
<p><em>In order to be considered as advanced electronic signature, a digital signature must be:</em></p>
<p>1- Uniquely linked to the signatory</p>
<p>2- Capable of identifying the signatory</p>
<p>3- Created using means under the sole control of the signatory</p>
<p>4- Linked to the data to which it relates</p>
<p><strong>An advanced electronic signature has more significant value than an electronic signature:</strong> it guarantees the integrity of the text, as well as the <strong>authentication</strong>.</p>
<p>However, the advanced electronic signature does not yet offer all the guaranties expected as regards to the protection of the signature creation data (data used by the signatory to create an electronic signature). This is why the EC introduced in the directive the qualified digital signature , reinforcing therfore the advanced signature by raising the quality and the control over its creation even further.</p>
]]></content:encoded>
			<wfw:commentRss>http://digitaltrustscience.com/legislation/advanced-signature/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Digital signature and legal aspects</title>
		<link>http://digitaltrustscience.com/legislation/digital-signature-and-legal-aspects/</link>
		<comments>http://digitaltrustscience.com/legislation/digital-signature-and-legal-aspects/#comments</comments>
		<pubDate>Tue, 16 Feb 2010 10:35:37 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[legislation]]></category>
		<category><![CDATA[accredited]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[certificate]]></category>
		<category><![CDATA[certification]]></category>
		<category><![CDATA[Digital signature]]></category>
		<category><![CDATA[European Parliament]]></category>
		<category><![CDATA[provider]]></category>
		<category><![CDATA[qualified]]></category>
		<category><![CDATA[service]]></category>

		<guid isPermaLink="false">http://digitaltrustscience.com/?p=87</guid>
		<description><![CDATA[<p>People who do business on the Internet require security and trust in electronic commerce and communication. You can&#8217;t see the person you are speaking with, you can&#8217;t see the documents that prove one&#8217;s identity, and you can&#8217;t even know if the web site you are connected to belongs to the organisation it says it does.</p> [...]]]></description>
			<content:encoded><![CDATA[<p>People who do business on the Internet require security and trust in electronic commerce and communication. You can&#8217;t see the person you are speaking with, you can&#8217;t see the documents that prove one&#8217;s identity, and you can&#8217;t even know if the web site you are connected to belongs to the organisation it says it does.</p>
<p><strong>Directive 1999/93/EC of the European Parliament and the council of December 13, 1999</strong></p>
<p>To answer these juridical necessities, the European Union adopted a community framework for electronic signatures some time ago (directive 1999/93/EC of the European Parliament and the council of December 13, 1999) that has been implemented in various European countries. The European directive is used for business in which European partners (persons or societies) or public administrations are involved. It also means that if an American organization enters into an electronic contract with a European society it has to respect European requirements to ensure the contract is valid.</p>
<p>The directive 1999/99/EC defines, in article 5, the electronic signature as follow:</p>
<p>&#8220;[..] Member States shall ensure that an electronic signature is not denied legal effectiveness and admissibility as evidence in legal proceedings solely on the grounds that it is:</p>
<p>1- in electronic form, or</p>
<p>2- not based upon a qualified certificate, or</p>
<p>3- not based upon a qualified certificate issued by an accredited certification-service-provider, or</p>
<p>4- not created by a secure signature-creation device. [..]&#8221;</p>
<p>Nevertheless, it remains essential to guaranty a signature&#8217;s effectiveness to ensure its value. This is why this very same european directive also draws the contours of stronger electronic signatures, admissible as evidence in legal proceedings: the advanced electronic signature and the even more legally admissible qualified digital signature (also called a secure digital signature or strong digital signature).</p>
]]></content:encoded>
			<wfw:commentRss>http://digitaltrustscience.com/legislation/digital-signature-and-legal-aspects/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Electronic signature</title>
		<link>http://digitaltrustscience.com/legislation/electronic-signature/</link>
		<comments>http://digitaltrustscience.com/legislation/electronic-signature/#comments</comments>
		<pubDate>Tue, 16 Feb 2010 10:24:26 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[legislation]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[cryptography]]></category>
		<category><![CDATA[Electronic signature]]></category>
		<category><![CDATA[paper]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[verified]]></category>
		<category><![CDATA[works]]></category>

		<guid isPermaLink="false">http://digitaltrustscience.com/?p=83</guid>
		<description><![CDATA[<p>Data in electronic form which are attached to or logically associated with other electronic data and which serve as a method of authentication (Article 2 of 93/1999/EC).</p> <p>How Digital Signature Technology Works</p> <p>Digital signature technology generally surpasses paper technology in all these attributes. To understand why, one must first understand how digital signature technology works.</p> [...]]]></description>
			<content:encoded><![CDATA[<p>Data in electronic form which are attached to or logically associated with other electronic data and which serve as a method of authentication (Article 2 of 93/1999/EC).</p>
<p><strong>How Digital Signature Technology Works</strong></p>
<p>Digital signature technology generally surpasses paper technology in all these attributes. To understand why, one must first understand how digital signature technology works.</p>
<p>Digital signatures are created and verified by cryptography, the branch of applied mathematics that concerns itself with transforming messages into seemingly unintelligible forms and back again. Digital signatures use what is known as &#8220;public key cryptography,&#8221; which employs an algorithm using two different but mathematically related &#8220;keys;&#8221; one for  creating an electronic signature (in other words transforming data into a seemingly unintelligible form), and another key for verifying a digital signature or returning the message to its original form.</p>
<p>Even so this is the most commonly accepted way to produce an electronic signature, it is not the only one.  evidencecube supports all known types of electronic signature: its technology-dependent architecture ensure the compatibility of the service to future digital signature implementations.</p>
]]></content:encoded>
			<wfw:commentRss>http://digitaltrustscience.com/legislation/electronic-signature/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The legislation</title>
		<link>http://digitaltrustscience.com/legislation/the-legislation/</link>
		<comments>http://digitaltrustscience.com/legislation/the-legislation/#comments</comments>
		<pubDate>Mon, 15 Feb 2010 09:21:05 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[legislation]]></category>
		<category><![CDATA[legal]]></category>
		<category><![CDATA[transactions]]></category>

		<guid isPermaLink="false">http://digitaltrustscience.com/?p=74</guid>
		<description><![CDATA[<p>&#8220;[..] The formal requirements for legal transactions, including the need for signatures, vary in different legal systems, and also vary with the passage of time. There is also variance in the legal consequences of failure to cast the transaction in a required form. The statute of frauds of the common law tradition, for example, does [...]]]></description>
			<content:encoded><![CDATA[<p>&#8220;[..] The formal requirements for legal transactions, including the need for signatures, vary in different legal systems, and also vary with the passage of time. There is also variance in the legal consequences of failure to cast the transaction in a required form. The statute of frauds of the common law tradition, for example, does not render a transaction invalid for lack of a &#8220;writing signed by the party to be charged,&#8221; but rather makes it unenforceable in court, a distinction which has caused the practical application of the statute to be greatly limited in case law.</p>
<p>During this century, most legal systems have reduced formal requirements, or at least have minimized the consequences of failure to satisfy formal requirements. Nevertheless, sound practice still calls for transactions to be formalized in a manner which assures the parties of their validity and enforceability. [..]</p>
<p>Although the basic nature of transactions has not changed, the law has adapted to advances in technology. The legal and business communities continue developing rules and practices which use new technology to achieve and surpass the effects historically expected from paperforms. [..]&#8221;</p>
<p>Extract from the American Bar Association website ( <a href="http://www.abanet.org" target="_blank">http://www.abanet.org</a> )</p>
<p>In 1999, The EC submitted a proposal to its members states through the  European Directive 1999/93/EC regarding the electronic signature which was retranscribed by them over the following years.</p>
<p>Similarily, the American  Electronic Signatures in Global and National Commerce Act (E-Sign) in June 2000 was designed to support the growth of e-business by mandating that electronic signatures (whether in interstate or foreign commerce) are given the same legal weight as traditional formats.</p>
<p>In other words, laws and legislations have been adapted around the world to give the electronic signature the same value as the hand-written signature.</p>
]]></content:encoded>
			<wfw:commentRss>http://digitaltrustscience.com/legislation/the-legislation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

