# Insecure param does not complete disable verification
**URL:** https://discuss.elastic.co/t/insecure-param-does-not-complete-disable-verification/334549
**Category:** Elastic Agent
**Tags:** elastic-stack-security, fleet
**Created:** [May 29, 2023, 5:01am UTC](https://discuss.elastic.co/t/insecure-param-does-not-complete-disable-verification/334549 "2023-05-29T05:01:08Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@kmahyyg](https://discuss.elastic.co/u/kmahyyg)
#### Post date: [May 29, 2023, 5:01am UTC](https://discuss.elastic.co/t/insecure-param-does-not-complete-disable-verification/334549/1 "2023-05-29T05:01:08Z")
I use `--insecure` when enrolling agent into fleet server in development environment. With some unable-to-say restrictions, this development environment cannot connect to CRL server.
However, in current environment, the `curl -v https://my-server:8220/api/status` returns fine on unix OS, since they does NOT check CRL on connection establishment. The certificate and CA are already trusted on OS level.
In windows, even I disabled CRL check in Internet Settings and rebooted, the curl will still give me this error: `schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.`
Since the elastic-agent and elastic-defend are using Golang/libcurl (in cpp) and do NOT give that detailed information, I've managed to find the root cause using a lot of time.
Please also set `--insecure` to disable OCSP and CRL check, thanks.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 26, 2023, 5:01am UTC](https://discuss.elastic.co/t/insecure-param-does-not-complete-disable-verification/334549/2 "2023-06-26T05:01:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.