Legitimate cryptography development incorrectly blocked by cyber safety classifier

Open 💬 1 comment Opened Jul 16, 2026 by ychromosome

What version of Codex CLI is running?

0.144.4

What subscription do you have?

Pro Lite

Which model were you using?

gpt-5.6-sol

What platform is your computer?

Fedora 43, x86_64, Kernel 7.1.3-100.fc43.x86_64

What terminal emulator and version are you using (if applicable)?

VTE 0.82.3

Codex doctor report

What issue are you seeing?

During legitimate defensive cryptography development, Codex displayed:
“This content can't be shown. We take extra caution with cybersecurity requests.”
The project is a private, local implementation of an elliptic-curve OpenSSL provider, including constant-time review, coverage-guided fuzzing, and portability testing on a user-owned Raspberry Pi. No scanning, exploitation, credential access, persistence, or third-party systems were involved. This appears to be a false positive caused by the combination of cryptography, SSH administration, side-channel review, and fuzz testing.

What steps can reproduce the bug?

Uploaded thread: 019f5181-8c92-7231-ba37-d76199765e7a

What is the expected behavior?

Legitimate defensive development and testing in a user-owned environment should continue normally. If additional verification is needed, the interface should explain that without hiding the response.

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗