Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
oscam
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
common
oscam
Merge requests
!70
Introduce binary signing
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
Introduce binary signing
binary-signing
into
master
Overview
0
Commits
39
Pipelines
11
Changes
7
Merged
WXbet
requested to merge
binary-signing
into
master
6 months ago
Overview
0
Commits
39
Pipelines
11
Changes
7
Expand
Build process
new build option WITH_SIGNING supported by make and cmake
create CA certificate (
config.sh --create-cert
) or use own pre-built certificate (
config.sh --add-cert
)
embed certificate as
config_cert
variable to config.c (
config.sh --make-config.mak
)
sign SHA1 hash of binary with private key after build
append signature to binary (upx binaries are supported as well)
build process uses the new options in config.sh (--create-cert, --add-cert, --cert-file, --cert-info, --sign-marker)
Runtime signature verification
extract public key from built-in certificate
read signature from running binary
verify SHA1 hash of running binary with extracted public key against signature
stop running oscam if the verification process fails
Runtime certificate/signature information
oscam startlog informs about signature verification status and certificate validity
oscam.version shows signature and certificate details
Edited
6 months ago
by
WXbet
1
0
Merge request reports
Loading