Creating Digitally Signed Content - GWWiki

                          Page   
                         Discussion   
                         View source   
                         History
-                Creating Digitally Signed Content - GWWiki
                
                            
            
                
                                
                    (Difference between revisions)
                                                            Jump to: navigation, search
                    
                    
			
			
			
			
		
		Revision as of 14:47, 7 July 2011 (view source)
Root  (Talk | contribs)
← Older edit
		Revision as of 15:05, 7 July 2011 (view source)
Root  (Talk | contribs) 
Newer edit →
		
Line 1:
Line 1:
  <div style="text-align: center;"> Creating Digitally Signed Content </div>   <div style="text-align: center;"> Creating Digitally Signed Content </div>
    
− Providing reliable content to end users is an important part of app development, especially considering apps that have paid features or other elements that depend on trusted information. This article provides detailed instructions for creating secure, digitally signed content for use with such apps. + Providing reliable content to end users is an important part of app development, especially considering apps that have paid features or other elements that depend on trusted information. This article provides detailed instructions for creating secure, digitally signed content and testing its validity.
    
− Digital signatures are often used to offer assurance that content came from a known source, and that it has not been tampered with. A digital signature can be verified by a certificate authority CA (A CA is "a trusted third party that is trusted by both the subject (owner) of the certificate and the party relying upon the certificate" source:[http://wikipedia.com wikipedia]). + * A Real World Example *
  +  
  + Mary, app developer for Contrary, Inc., has been told to create an app that will run as a demo until the end user pays for a license. Once a license it obtained, and installed, the app should run without any restrictions. 
  +  
  + * Your Own Digital Certificate *
  +  
  + Digital signatures are often used to offer assurance that content came from a known source, and that it has not been tampered with. A digital signature can be verified by a [http://en.wikipedia.org/wiki/Certificate_authority certificate authority] or can be [http://en.wikipedia.org/wiki/Self-signed_certificate self-signed]. 
  +  
  + For the purposes of signing content specifically for app use, having a digital signature verified by a CA is unnecessary. After all, the communication path will be between the developer and the app, and will not involve any other party.
Revision as of 15:05, 7 July 2011
 Creating Digitally Signed Content 
Providing reliable content to end users is an important part of app development, especially considering apps that have paid features or other elements that depend on trusted information. This article provides detailed instructions for creating secure, digitally signed content and testing its validity.

 A Real World Example *

Mary, app developer for Contrary, Inc., has been told to create an app that will run as a demo until the end user pays for a license. Once a license it obtained, and installed, the app should run without any restrictions. 

 Your Own Digital Certificate *

Digital signatures are often used to offer assurance that content came from a known source, and that it has not been tampered with. A digital signature can be verified by a certificate authority or can be self-signed. 
For the purposes of signing content specifically for app use, having a digital signature verified by a CA is unnecessary. After all, the communication path will be between the developer and the app, and will not involve any other party.

Retrieved from "http://www.gwmicro.com/mediawiki/index.php/Creating_Digitally_Signed_Content"
+Text Size:
 

                	
		Navigation
		
			
				Main page
				Recent changes
				Random page
				Help
			
		
	
	
		Search
		
			
				
				 
				
			
		
	
	
		Toolbox
		
			
				What links here
				Related changes
Special pages
				Printable version
				Permanent link
			
		
	
                
                    Personal tools
                    
                        
Log in / create account
@@ Line 1: / Line 1: @@
 <div style="text-align: center;"> Creating Digitally Signed Content </div>
-Providing reliable content to end users is an important part of app development, especially considering apps that have paid features or other elements that depend on trusted information. This article provides detailed instructions for creating secure, digitally signed content for use with such apps.
+Providing reliable content to end users is an important part of app development, especially considering apps that have paid features or other elements that depend on trusted information. This article provides detailed instructions for creating secure, digitally signed content and testing its validity.
-Digital signatures are often used to offer assurance that content came from a known source, and that it has not been tampered with. A digital signature can be verified by a certificate authority CA (A CA is "a trusted third party that is trusted by both the subject (owner) of the certificate and the party relying upon the certificate" source:[http://wikipedia.com wikipedia]).
+* A Real World Example *
+Mary, app developer for Contrary, Inc., has been told to create an app that will run as a demo until the end user pays for a license. Once a license it obtained, and installed, the app should run without any restrictions.
+* Your Own Digital Certificate *
+Digital signatures are often used to offer assurance that content came from a known source, and that it has not been tampered with. A digital signature can be verified by a [http://en.wikipedia.org/wiki/Certificate_authority certificate authority] or can be [http://en.wikipedia.org/wiki/Self-signed_certificate self-signed].
+For the purposes of signing content specifically for app use, having a digital signature verified by a CA is unnecessary. After all, the communication path will be between the developer and the app, and will not involve any other party.