anchore / anchore/syft

binary detection: openbsd OpenSSH and portable OpenSSH

Open
#3,216 3 comments 0 reactions 0 assignees View on GitHub
binary-analysis enhancement
Dominant language
Go
Stars
9.6k
Forks
962
Avg merge
23h 27m
Merged PRs (30d)
48

Description

Hi,

(Not sure if i'm right here, because it's a contributor question and i'm not so familiar with go)

I would like to implement openbsd OpenSSH and portable OpenSSH binary detection with correct cpe's in one classifier.

So openbsd have two OpenSSH products with different cpe's:
- [normal](https://nvd.nist.gov/products/cpe/detail/DE876FD6-4D26-463F-886E-6A53DE98835B?namingFormat=2.3&orderBy=CPEURI&keyword=cpe%3A2.3%3Aa%3Aopenbsd%3Aopenssh&status=FINAL) `cpe:2.3:a:openbsd:openssh:9.6:-:*:*:*:*:*:*`
- [portable](https://nvd.nist.gov/products/cpe/detail/64848251-5FCD-476A-B2AB-744B23F6243F?namingFormat=2.3&orderBy=CPEURI&keyword=cpe%3A2.3%3Aa%3Aopenbsd%3Aopenssh&status=FINAL) `cpe:2.3:a:openbsd:openssh:9.6:p1:*:*:*:*:*:*`

I alrady have the regex to match the version `\x00OpenSSH_(?P[0-9]+\.[0-9]+)(p[0-9])?\x00` (is also match the optional portable `p1` information).

The question ist: how can I build this two different cpe in one classifier?
Is it possible to implement this with one classifier? If not I will make simply two classifyers: openssh-binary and openssh-portable-binary.

Thanks

Contributor guide

Open the contributing guide

Research direction

The issue names no source file or test; start by locating Syft's binary-classifier entry point and comparing existing CPE handling. Use the supplied OpenSSH version regex and CPE examples as the expected inputs, with completion meaning normal and portable OpenSSH produce their respective CPEs.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.