コード署名と公証
ユーザーの信頼とセキュリティ要件への準拠を確保するため、Windowsのコード署名とmacOSの公証が重要な理由を理解します。
「コード署名と公証」はCoddyKit上の無料Electron Desktop App Developmentレッスンです。 これはレッスン2/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。 これはElectron Desktop App Development学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Electron Desktop App Developmentコースには全4レッスンが含まれています。
このレッスンの一部はまだ翻訳されておらず、英語で表示されています。
Building Trust with Code Signing
When you distribute your Electron app, users need to trust it. Operating systems like Windows and macOS have built-in security features to protect users from malicious software.
Code signing and notarization are essential steps to prove your app's authenticity and integrity, ensuring users feel safe installing it.
What is Code Signing?
Code signing is like attaching a digital signature to your application. It uses a cryptographic certificate issued by a trusted Certificate Authority (CA).
- Authenticity: Verifies the app comes from you, the publisher.
- Integrity: Confirms the app hasn't been tampered with since you signed it.
If the signature is invalid or altered, the OS will warn the user.
Trust on Windows
On Windows, unsigned applications often trigger security warnings like "Windows protected your PC" (SmartScreen filter).
A valid code signature helps your app pass these checks, giving users confidence and reducing installation friction. It also allows your app to be installed without extra administrator prompts for some operations.
Signing Windows Executables
To sign your Windows Electron app, you'll need a Code Signing Certificate. This is typically a PFX file containing your private key and certificate chain.
Tools like electron-builder simplify this process by letting you specify your certificate details in the configuration.
{
"build": {
"win": {
"target": "nsis",
"signingHashAlgorithms": ["sha256"],
"signAndEditExecutable": true
},
"cscKeyPassword": "your-cert-password",
"cscInstallerPassword": "your-cert-password",
"cscLink": "path/to/your/certificate.pfx"
}
}Time-Stamping Your Signature
When code signing, it's crucial to also time-stamp your signature. This ensures that even if your signing certificate expires, the signature remains valid because it was signed when the certificate was active.
Most signing tools, including electron-builder, can automatically add a time-stamp server URL to your signing process.
macOS Notarization Explained
For macOS, Apple introduced Notarization as an additional security check. It's an automated service that scans your app for malicious content and code signature issues.
Think of it as Apple giving your app a "seal of approval" before it can run smoothly on macOS Catalina and later.
Meeting Apple's Gatekeeper
macOS's security feature, Gatekeeper, blocks unsigned or unnotarized apps from running by default. Users will see a warning that the app "cannot be opened because the developer cannot be verified."
Notarization allows your app to pass Gatekeeper checks without annoying users or requiring them to bypass security settings manually.
Getting Ready for Notarization
To notarize your Electron app, you need:
- An Apple Developer ID.
- An app-specific password for your Apple ID.
- Your app must be signed with a Developer ID Application certificate.
- Hardened Runtime enabled (a security feature).
electron-builder handles most of these configurations for you.
Notarizing with electron-builder
electron-builder simplifies the notarization process. You configure your Apple ID credentials and it handles uploading your app to Apple's notarization service.
It waits for the notarization to complete and then "staples" the notarization ticket to your app bundle.
{
"build": {
"mac": {
"hardenedRuntime": true,
"gatekeeperAssess": false,
"entitlementsInherit": "build/entitlements.mac.plist",
"entitlements": "build/entitlements.mac.plist"
},
"afterSign": "electron-builder-notarize"
}
}Secure & Automated Signing
Always keep your signing certificates and private keys secure. Treat them like sensitive passwords.
Integrate code signing and notarization into your Continuous Integration/Continuous Deployment (CI/CD) pipeline to automate the process and ensure every build is properly signed and notarized.
Check Your Knowledge
Which statements accurately describe the purpose or requirements of code signing and macOS notarization?
Recap: Trust & Security
In this lesson, we learned about the critical role of code signing for Windows and notarization for macOS in distributing your Electron applications.
These processes build user trust, ensure app integrity, and help your app run smoothly on target operating systems by satisfying their built-in security requirements.
よくある質問
「コード署名と公証」レッスンは無料ですか？
はい。「コード署名と公証」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Electron Desktop App Developmentコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Electron Desktop App Developmentコースには全4レッスンが含まれています。
「コード署名と公証」で何を学びますか？
ユーザーの信頼とセキュリティ要件への準拠を確保するため、Windowsのコード署名とmacOSの公証が重要な理由を理解します。 ブラウザで直接実行するハンズオンコードでElectron Desktop App Developmentを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。
Electron Desktop App Developmentを始めるのに経験は必要ですか？
事前経験は必要ありません。CoddyKitのElectron Desktop App Developmentは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン2/4です。
「コード署名と公証」レッスンにはどのくらい時間がかかりますか？
ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。
このElectron Desktop App Developmentレッスンでコードを書いて実行できますか？
はい。すべてのElectron Desktop App Developmentレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。