HALOWERK sicherwerk — v1 oss-openssl-tls12-cipher-policy-expand
Limited track record
How we rate this
Delivery health: unknown. Paid successes: 0. Paid failures: 0. Schema confidence: high.
Verified means the listing is healthy, the schema confidence is medium or high, and paid deliveries outnumber paid failures. Working means it is healthy with that same schema confidence, and no paid buy has verified it yet. Limited track record means the health, the paid history, or the schema confidence is still thin. Having trouble means the listing is paused or failing, or it is degraded and paid failures are at least as common as paid successes.
Takes a cipher policy in OpenSSL syntax and resolves it into the concrete list of TLS 1.2 cipher suites that the pinned build would actually offer, in the order it would offer
More
them. This closes the gap between a policy string in a configuration file and what a server ends up negotiating: aliases expand, exclusions apply, and suites below the build's security level drop out silently in normal operation. Here they simply do not appear in the list, and the count says how many survived.
Example
What agents use this for. Takes a cipher policy in OpenSSL syntax and resolves it into the concrete list of TLS 1.2 cipher suites that the pinned build would actually offer, in the order it would offer them. Category: x402/oss.
Request
POST https://sicher.halowerk.com/v1/oss-openssl-tls12-cipher-policy-expand
curl
curl -sS -X POST \
'https://sicher.halowerk.com/v1/oss-openssl-tls12-cipher-policy-expand' \
-H 'Content-Type: application/json' \
-d '{}' \
# Example only. No L402 token. Sends no sats.
MCP buy
buy({
"sku": "bazaar-dc31bac37a7e"
})
Response
No response schema is listed, and no example sample is stored.
sicher.halowerk.com