Skip to content

fix: test every trust path by default - #1

Merged
fproulx-boostsecurity merged 1 commit into
boostsecurityio:mainfrom
mrene:test-both-chains
Oct 22, 2026
Merged

fproulx-boostsecurity merged 1 commit into
boostsecurityio:mainfrom
mrene:test-both-chains

Conversation

@mrene

@mrene mrene commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

The default tested only the Sectigo cross-signed path. Mozilla-derived trust stores trust AAA Certificate Services for e-mail only, so a client can reject that path while still accepting the direct emSign path, and emBarrass reported such a vulnerable client as protected or inconclusive.

--chain now defaults to "all": emsign runs first, then sectigo. The result is vulnerable as soon as any path is accepted, rejected only if every path rejects, and otherwise inconclusive, naming the path its reason and child exit came from. No further path starts after cancellation. --timeout applies per path, each run is announced so consecutive child output stays separable, and batch logs the deciding path. --chain emsign|sectigo still runs the command once.

The default tested only the Sectigo cross-signed path. Mozilla-derived
trust stores trust AAA Certificate Services for e-mail only, so a client
can reject that path while still accepting the direct emSign path, and
emBarrass reported such a vulnerable client as protected or inconclusive.

--chain now defaults to "all": emsign runs first, then sectigo. The
result is vulnerable as soon as any path is accepted, rejected only if
every path rejects, and otherwise inconclusive, naming the path its
reason and child exit came from. No further path starts after
cancellation. --timeout applies per path, each run is announced so
consecutive child output stays separable, and batch logs the deciding
path. --chain emsign|sectigo still runs the command once.
@fproulx-boostsecurity

Copy link
Copy Markdown
Contributor

Love it thanks for the contrib @mrene

@fproulx-boostsecurity
fproulx-boostsecurity merged commit 74e5223 into boostsecurityio:main Oct 22, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants