# Sandbox module cannot be downloaded via extension manager today?

**URL:** <https://discourse.slicer.org/t/sandbox-module-cannot-be-downloaded-via-extension-manager-today/33809>\
**Category:** Support\
**Created:** [January 16, 2024, 10:39pm UTC](https://discourse.slicer.org/t/sandbox-module-cannot-be-downloaded-via-extension-manager-today/33809 "2024-01-16T22:39:02Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [January 26, 2024, 10:37pm UTC](https://discourse.slicer.org/t/sandbox-module-cannot-be-downloaded-via-extension-manager-today/33809/31 "2024-01-26T22:37:17Z")

</div>

> [@lassoan](#):
>
> Do you know why Slicer brings its own .crt file (instead of trying to get the certificates from the operating system)?

At the time it was implemented, it was the simplest way to have certificates across all platform. The `Slicer.crt` is generated from the Mozilla certificates similarly to the ones distributed through [python-certifi](https://github.com/certifi/python-certifi). They are also automatically maintained up-to-date using the [update-slicer-certificate-bundle.yml](https://github.com/Slicer/Slicer/blob/main/.github/workflows/update-slicer-certificate-bundle.yml) GitHub workflow.

We could revisit this so that Python, CURL and Qt all use certificates when from the system store on platform supporting it.

---

_[View the full topic](https://discourse.slicer.org/t/sandbox-module-cannot-be-downloaded-via-extension-manager-today/33809)._