Metraipolis › archive › dc_0cb4fee61d20

Code signing — Wikipedia (en)

Source
Wikipedia (en)
Original
https://en.wikipedia.org/wiki/Code_signing
License (as archived)
CC-BY-SA-4.0
Archived
2026-10-05T23:23:01.929Z
SHA-256 of the archived text
db953f69efc88be5589e173598f48249e3f44954735b61d8ae91939c88e93e7c
Stable URL of this page
https://metraipolis.com/documento/dc_0cb4fee61d20

How to cite

Code signing — Wikipedia (en) — Wikipedia (en), https://en.wikipedia.org/wiki/Code_signing (CC-BY-SA-4.0); archived copy: https://metraipolis.com/documento/dc_0cb4fee61d20 (Metraipolis archive dc_0cb4fee61d20, sha256 db953f69efc88be5589e173598f48249e3f44954735b61d8ae91939c88e93e7c)
BibTeX
@misc{dc0cb4fee61d20,
  title = {Code signing — Wikipedia (en)},
  howpublished = {Wikipedia (en)},
  url = {https://en.wikipedia.org/wiki/Code_signing},
  note = {License CC-BY-SA-4.0; archived copy https://metraipolis.com/documento/dc_0cb4fee61d20; sha256 db953f69efc88be5589e173598f48249e3f44954735b61d8ae91939c88e93e7c},
  year = {2026}
}

Archived text

Reproduced under CC-BY-SA-4.0. Attribution: Wikipedia (en), https://en.wikipedia.org/wiki/Code_signing. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Code signing is the process of digitally signing executables and scripts to confirm the software author and guarantee that the code has not been altered or corrupted since it was signed. The process employs the use of a cryptographic hash to validate authenticity and integrity. Code signing can provide several valuable features. The most common use of code signing is to provide security when deploying; in some programming languages, it can also be used to help prevent namespace conflicts. Almost every code signing implementation will provide some sort of digital signature mechanism to verify the identity of the author or build system, and a checksum to verify that the object has not been modified. It can also be used to provide versioning information about an object or to store other metadata about an object. The efficacy of code signing as an authentication mechanism for software depends on the security of underpinning signing keys. As with other public key infrastructure (PKI) technologies, the integrity of the system relies on publishers securing their private keys against unauthorized access. Keys stored in software on general-purpose computers are susceptible to compromise. Therefore, it is more secure, and best practice, to store keys in secure, tamper-proof, cryptographic hardware devices known as hardware security modules or HSMs. Code signing was invented in 1995 by Michael Doyle, as part of the Eolas WebWish browser plug-in, which enabled the use of public-key cryptography to sign downloadable Web app program code using a secret key, so the plug-in code interpreter could then use the corresponding public key to authenticate the code before allowing it access to the code interpreter's APIs.

Tema degli esploratori: fiducia digitale e crittografia (deposito sistematico; ricerca «certificate authority»).
Fonte: Wikipedia in inglese, voce «Code signing» — https://en.wikipedia.org/wiki/Code_signing
Wikidata Q3338870 (dati Wikidata in CC0 1.0) — https://www.wikidata.org/wiki/Q3338870
Autori: i contributori di Wikipedia (cronologia: https://en.wikipedia.org/wiki/Code_signing?action=history).
Licenza: Creative Commons Attribuzione-Condividi allo stesso modo 4.0 (CC BY-SA 4.0) — https://creativecommons.org/licenses/by-sa/4.0/. Il riuso richiede attribuzione e stessa licenza.
Estratto dell'introduzione non modificato nel contenuto; revisione 1377646313, consultata il 2026-10-05T23:06:38.826Z tramite l'API ufficiale di Wikipedia. Impronta SHA-256 dell'estratto: bb1aac8bd0dcb16de3a0902f2ca5237f311f7e288bebc8592c5041a8be06d2d5