FEDORA-2016-527018d2ff

Notes about this update:

Related Bugs 3

Comments 8 RSS

• bodhi 7 months ago, 2016-01-28 17:14:26 (UTC)

  This update has been submitted for testing by tmraz.
• dhgutteridge 7 months ago, 2016-01-28 19:08:50 (UTC)

  No issues noted.

  karma: +1

  ---

  critpath: +1

  ---

• bodhi 7 months ago, 2016-01-29 01:53:05 (UTC)

  This update has been pushed to testing.
• bodhi 7 months ago, 2016-01-29 06:41:58 (UTC)

  This update has been submitted for stable by bodhi.
• cserpentis 7 months ago, 2016-01-29 06:41:59 (UTC)

  works for me

  karma: +1

  ---

• xenithorb 7 months ago, 2016-01-30 08:59:40 (UTC)

  no noticeable regressions

  karma: +1

  ---

  critpath: +1

  ---

• pnemade 7 months ago, 2016-01-30 13:25:19 (UTC)

  looks good

  karma: +1

  ---

  critpath: +1

  ---

• bodhi 7 months ago, 2016-01-30 18:23:10 (UTC)

  This update has been pushed to stable.

Email

Comment

Comment fields support Fedora-Flavored Markdown.

×

Fedora-Flavored Markdown

Text fields in Bodhi2 support an enhanced version of markdown. This is a cheat sheet for your reference.

---

You can do headers by underlining or by prefixing with the # character:

This is an H1
=============

This is an H2
-------------

# This is another H1

## This is another H2

---

You can do blockquotes using email-style prefixes with the > character:

> This is a quotation
> over many lines
> > and it can be nested(!)

---

Lists work like you'd expect, by prefixing with any of the *, +, or - characters:

Check out this list:

* This
* is
* a list..

You need a blank line between a paragraph and the start of a list for the renderer to pick up on it.

Emphasis can be added like this:

*italics*
_italics_
**bold**
__bold__

---

You can save your code references from being misinterpreted as emphasis by surrounding them with backtick characters (`):

Use `the_best_function()` and _not_ that crummy one.

---

Links look like this:

[text](http://getfedora.org)

..but we also support bare links if you just provide a URL.

---

You can create code blocks by indenting every line of the block by at least 4 spaces or 1 tab.

Here is a code block:

    for i in range(4):
        print i
    print "done."

You can reference bug reports by simply writing something of the form tracker#ticketid.

This fixes PHP#1234 and Python#2345

... we will automatically generate links to the tickets in the appropriate trackers in place.

The supported bug tracker prefixes are: (these are all case-insensitive)

• Fedora, RHBZ and RH (all point to the Red Hat Bugzilla)
• GNOME
• KDE
• PEAR
• PHP
• Python

---

And you can refer to other users by prefixing their username with the @ symbol.

Thanks @mattdm!

This will generate a link to their profile, but it won't necessarily send them a notification unless they have a special FMN rule set up to catch it.

---

Lastly, you can embed inline images with syntax like this:

![Alt text](/path/to/img.jpg)

You can read much more about markdown syntax at daringfireball.net.

Preview

Preview

Arithmetic

Solution

Feedback

			#1301846 CVE-2015-3197 OpenSSL: SSLv2 doesn't block disabled ciphers
			#1301845 CVE-2016-0701 OpenSSL: DH small subgroups
			#1302767 CVE-2015-3197 OpenSSL: SSLv2 doesn't block disabled ciphers [fedora-all]
			Does the system's basic functionality continue to work after this update?
			Is the update generally functional?

Add Comment