# Is there a version that addresses sweet32

**URL:** https://meta.discourse.org/t/is-there-a-version-that-addresses-sweet32/54227
**Category:** Support
**Created:** [14.Декабрь.2016 10:02:21 UTC](https://meta.discourse.org/t/is-there-a-version-that-addresses-sweet32/54227 "2016-12-14T10:02:21Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![gearoid](https://avatars.discourse-cdn.com/v4/letter/g/9f8e36/32.png) [@gearoid](https://meta.discourse.org/u/gearoid)
#### Post date: [14.Декабрь.2016 10:02:21 UTC](https://meta.discourse.org/t/is-there-a-version-that-addresses-sweet32/54227/1 "2016-12-14T10:02:21Z")

</div>

Was reading this [post](https://meta.discourse.org/t/meta-discourse-org-issue-on-firefox/49350) was a change made in a particular version that addressed sweet32 ?

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [14.Декабрь.2016 10:34:52 UTC](https://meta.discourse.org/t/is-there-a-version-that-addresses-sweet32/54227/2 "2016-12-14T10:34:52Z")

</div>

This has nothing to do with Discourse, the software.

It was mitigated by updating the cipher suite we use for our SSL certificates for **our** servers.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [14.Декабрь.2016 10:36:22 UTC](https://meta.discourse.org/t/is-there-a-version-that-addresses-sweet32/54227/3 "2016-12-14T10:36:22Z")

</div>