Self Signed Software Self Signed Certificates Signing Certificates Differences

There are three types of signatures:

Symbian signature.

That is, the official signature of the Symbian mobile phone operating system. Only software that has passed the Symbian security certification will receive Symbian's.

Signature. This type of software has the highest level of security. It can be installed and run normally on the mobile phone and can realize all the functions provided by the software.

Obtaining a Symbian signature requires the author of the software to deal directly with the Symbian authorities, and for a number of reasons, not all software authors are capable of obtaining this certification.

Signature of the author. The software is signed by the software author when it is released. This type of software can be installed and run on mobile phones (security may be encountered.

Sex warning, skippable). However, it is not possible to implement those functions that are "specifically restricted". If a piece of software doesn't cover this kind of functionality at all, then.

It's entirely possible for the software author to sign it himself. There is also the possibility that some of the software's functions are "specifically limited".

scope, but not the main feature. The author of the software may also release an "author-signed version" that will work for the most part.

functionality, but some specific features will be lost. For example, there is such a version of the "Callitcom" software, almost all the functions can be used, but it can't.

Auto-start at boot.

User signatures. (It's the kind that the certificate area uses now, and the signature here refers to this, and the certificate refers to this).

Strictly speaking, this should be a "developer signature". Because Symbian provides software developers with a kind of "development certificate", the original meaning is.

It is used by software developers for software testing. This "development certificate" is linked to the IMEI code of the machine being used for testing. Use this.

The certificate-signed software can only be used on the machine corresponding to the IMEI code, and cannot be used on other machines.

What we call "self-signing" is actually using this method, to put it bluntly, you say that you are developing software, and you provide you with a test machine.

IMEI code, Symbian issues you a "development certificate" that you use to sign your "test software". Yourself to yourself.

The "development behavior" is responsible! So much for. In addition, the development certificate is valid for six months from the date of issuance. However, it has been signed within the validity period of the certificate.

There is no limit to the time limit for which the program can be used.

I don't really understand, anyway, I just use a signing software, plus a certificate. The so-called self-signature is to sign it yourself

What is a Signing Certificate?

A signing certificate is the process of digitally signing executable programs and scripts to confirm the identity of the software author and to ensure that it has not been modified or corrupted since signing. In order to sign **, the software publisher needs to generate a private public key pair, submit the public key to the CA, and issue a request for the signing certificate. The CA verifies the identity of the publisher and validates the publisher's request for a digitally signed certificate.

If this is audited and the key is verified, the CA will issue a signing certificate.

With the signing certificate, the publisher can sign it. When signed, some information is added to the original file containing the executable, and the software publisher's users use these bound information to authenticate the publisher and check for tampering with the signature.

How do users know if they trust the software?

To help users determine whether they can trust the software before installing it, software publishers can digitally sign their **. The digital signature verifies the identity of the author of the software and has not been tampered with. Signed certificates are issued by a trusted third-party authority, CA, and are more reliable than unsigned.

What are the types of signing certificates?

**Signing certificate is divided into ordinary ** signing certificate and enhanced ** signing certificate, without ** signing certificate, Microsoft will issue a warning, accompanied by an unknown publisher reminder, install ** signing certificate can eliminate the security warning of the system "unknown developer".

Normal** signing certificates will display the enterprise name in the certificate, while enhanced ** signing certificates will display the enterprise name, enterprise address, and enterprise type in the certificate.

Digitally signing software can solve the problem of counterfeit software acting as a genuine version to deceive users, so that users can intuitively distinguish the authenticity of the software, which can effectively protect the rights and interests of legitimate software developers and users. At the same time, the digital signature of the software can also make the brand of the software enterprise get the most in front of the user. Reference:

Why digitally sign software.

A self-signed certificate is a certificate signed by the same entity that issued the certificate. A self-signed certificate is a certificate that has signed its own private key. You can use the Certificate Assistant in Keychain Access to create your own self-signed certificates.

Apple generates a pair of keys, the public key is installed on each iOS device, the private key is stored in the Apple background server, when the APP is put on the AppStore, the Apple background signs (encrypts) the APP with the private key, when the user uses the iOS device cavity **APP, the public key in the device is used to verify the signature, if the signature is correct, then the APP can be considered to be officially certified.

The specific composition of Apple's self-signed:

Technically, the certificate actually contains three parts, the user's information, the user's public key, and the CA center's signature on the information in the certificate. To verify the authenticity of a certificate (i.e., to verify whether the CA center's signature on the certificate information is valid), it is necessary to verify with the public key of the CA center, and the public key of the CA center exists in the certificate that signs the trembling shirt certificate, so the certificate is required.

However, the use of the certificate to verify the authenticity of the certificate itself needs to be verified, so it is necessary to use the certificate issued to verify, so that it constitutes a certificate chain relationship, the answer is the root certificate, the root certificate is a special certificate, its issuer is itself, ** the root certificate indicates that you trust the certificate issued below the root certificate.