# March 2015 OpenSSL updates

**URL:** https://meta.discourse.org/t/march-2015-openssl-updates/26546
**Category:** Self-hosting
**Tags:** docker
**Created:** [March 19, 2015, 7:31pm UTC](https://meta.discourse.org/t/march-2015-openssl-updates/26546 "2015-03-19T19:31:24Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)
#### Post date: [March 19, 2015, 7:31pm UTC](https://meta.discourse.org/t/march-2015-openssl-updates/26546/1 "2015-03-19T19:31:24Z")

</div>

Continuing the discussion from [Patching the heartbleed vuln in a docker image?](https://meta.discourse.org/t/patching-the-heartbleed-vuln-in-a-docker-image/14574):

Today OpenSSL announced a big list of vulnerabilities and updated releases for those vulnerabilities:

> **[Vulnerabilities | OpenSSL Library](https://openssl-library.org/news/vulnerabilities/index.html)**

What is the suggested plan for upgrading? Will there be a new Docker image? Should admins plan to go in and update OpenSSL manually somehow?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 19, 2015, 8:13pm UTC](https://meta.discourse.org/t/march-2015-openssl-updates/26546/2 "2015-03-19T20:13:27Z")

</div>

There will be a new docker image, just need to confirm the updates don’t break us.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [June 8, 2024, 12:46pm UTC](https://meta.discourse.org/t/march-2015-openssl-updates/26546/3 "2024-06-08T12:46:10Z")

</div>

This topic was automatically closed after 3368 days. New replies are no longer allowed.