blog/alert subpages

2018-04-06 14:05:27 +02:00 · 2018-04-06 14:05:27 +02:00 · fc885252c2
commit fc885252c2
parent 0f8bb81f88
13 changed files with 227 additions and 38 deletions
--- a/_alerts/2012-03-16-critical-vulnerability.html
+++ b/_alerts/2012-03-16-critical-vulnerability.html
@ -1,10 +1,12 @@
 ---
 title: "Potentially Critical Security Vulnerability"
 shorturl: "critfix"
+show_toc: true
 active: false
 banner: ""
 date: 2012-03-16
 ---
+<div class="post-content" markdown="1">
 <p>
 A potential security vulnerability has been discovered in the Windows
 version of Bitcoin-Qt. If you are running Bitcoin-Qt versions 0.5
@ -30,7 +32,9 @@ href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/"
 href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/">
 0.5.3.1 for Windows and 0.5.3 for Linux</a>
 </p>
+</div>

+<div class="toccontent-block boxexpand" markdown="1">
 <h3 id="spanish">Español: Vulnerabilidad de seguridad (potencialmente crítica)</h3>
 <p>
 Una vulnerabilidad de seguridad posible no son afectadas en la versión Windows de Bitcoin-Qt. Si está utilizando Bitcoin-Qt 0.5 a través de las versiones 0.6 en Windows, debe cerrar y actualizar a la versión 0.5.3.1 o 0.6rc4 AHORA.
@ -49,7 +53,9 @@ href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/"
 href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/">
 0.5.3.1 para Windows y 0.5.3 para Linux</a>
 </p>
+</div>

+<div class="toccontent-block boxexpand" markdown="1">
 <h3 id="german">Deutsch: DRINGEND: Windows Bitcoin-Qt update</h3>
 <p>
 Es wurde eine potenzielle Schwachstelle in der Windowsversion Qt-Bitcoin entdeckt. Wenn Sie mit Bitcoin-Qt-Versionen 0.5 bis 0.6 unter Windows arbeiten, sollten Sie das Programm beenden und ein Upgrade auf entweder Version 0.5.3.1 oder 0.6rc4 JETZT durchführen.
@ -70,7 +76,9 @@ href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/"
 href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/">
 0.5.3.1 für Windows und 0.5.3 für Linux</a>
 </p>
+</div>

+<div class="toccontent-block boxexpand" markdown="1">
 <h3 id="dutch">Nederlands: Mogelijk kritisch veiligheidsprobleem</h3>
 <p>
 Er is een een mogelijk veiligheidsprobleem gevonden in de Windows versie van
@ -97,7 +105,9 @@ href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/"
 href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/">
 0.5.3.1 voor Windows en 0.5.3 for Linux</a>
 </p>
+</div>

+<div class="toccontent-block boxexpand" markdown="1">
 <h3 id="russian">Русский: Найдена потенциальная критическая уязвимость в версиях Bitcoin-Qt от 0.5 до 0.6 для Windows</h3>
 <p>
 Найдена потенциальная критическая уязвимость в версиях Bitcoin-Qt от 0.5 до 0.6 для Windows. Если вы используете одну из этих версий, отключите её и обновитесь до 0.5.3.1 или 0.6rc4 немедленно.
@ -117,7 +127,9 @@ href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/"
 href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/">
 0.5.3.1</a>
 </p>
+</div>

+<div class="toccontent-block boxexpand" markdown="1">
 <h3 id="italian">Italiano: Potenziale vulnerabilità di sicurezza critica.</h3>
 <p>
 Una potenziale vulnerabilità di sicurezza è stata scoperta nella versione di Windows di Bitcoin-Qt. Se stai usando Bitcoin-Qt su Windows dalle versioni 0.5 alla 0.6 dovresti chiuderla e aggiornarla alle versioni 0.5.3.1 o 0.6rc4 ORA.
@ -134,7 +146,9 @@ href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/"
 href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/">
 0.5.3.2 per Windows e 0.5.3 per Linux</a>
 </p>
+</div>

+<div class="toccontent-block boxexpand" markdown="1">
 <h3 id="portugese">Português: Vulnerabilidade de segurança potencialmente crítica</h3>
 <p>
 Uma vulnerabilidade de segurança em potencial foi descoberto na versão do Bitcoin-Qt para Windows. Se você estiver executando alguma versão entre a 0.5 até a 0.6 do Bitcoin-Qt no Windows, você deve desligá-lo e atualizá-lo para a versão 0.5.3.1 ou 0.6rc4 AGORA!
@ -155,7 +169,9 @@ href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/">
 </p><p>
 Traduzido por Thiago Martins (ThiagoCMC)
 </p>
+</div>

+<div class="toccontent-block boxexpand" markdown="1">
 <h3 id="polish">Polski: Potencjalnie Krytyczne Zagrozenie Bezpieczenstwa</h3>
 <p>
 Potencjalne zagrozenie zostalo odkryte w Bitcoin-QT wersji Windows. Jesli masz uruchomiony Bitcoin-Qt w wersjach 0.5 przez 0.6 w wersji Windows powinienes je zamknac i pobrac najnowsze wersje 0.5.3.1 lub 0.6rc4 TERAZ.
@ -174,7 +190,9 @@ href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/"
 href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/">
 0.5.3.1 dla WIndows  i 0.5.3 dla Linuxa</a>
 </p>
+</div>

+<div class="toccontent-block boxexpand" markdown="1">
 <h3 id="bulgarian">Български език: Уязвимост в сигурността.</h3>
 <p>
 Уязвимост в сигурността бе открита при Windows версията на Bitcoin-Qt.Ако използвате Bitcoin-Qt версия 0.5 до 0.6 през Windows,ще се наложи да я спрете и да направите ъпгрейд  до 0.5.3.1 или 0.rc4.Command-line даемон-а(bitcoind),няма да бъде афектиран за потребители на Mac или Linux.Поради вида на тази уязвимост,ние вярваме,че би могло да бъде доста трудно за атакуващия да направи нещо повече от това да crash-не  процесът - Bitcoin-Qt.Поради това ние го считаме за критичен проблем.
@ -190,7 +208,9 @@ href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/"
 href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/">
 0.5.3.1 за Windows и 0.5.3 за Linux.</a>
 </p>
+</div>

+<div class="toccontent-block boxexpand" markdown="1">
 <h3 id="greek">Ελληνικά: Σοβαρό πρόβλημα ασφάλειας</h3>
 <p>
 Ένα πιθανά σοβαρό πρόβλημα ασφάλειας εντοπίστηκε στην έκδοση Windows του Bitcoin-Qt. Εαν χρησιμοποιείτε Bitcoin-Qt εκδόσεις 0.5 έως 0.6 στα Windows, αναβαθμήστε <b>άμεσα</b> σε έκδοση 0.5.3.1 ή 0.6rc4.
@ -208,7 +228,9 @@ href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/"
 href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/">
 0.5.3.1 για Windows και 0.5.3 για Linux</a>
 </p>
+</div>

+<div class="toccontent-block boxexpand" markdown="1">
 <h3 id="swedish">Svenska: Potentiellt kritiskt säkerhetshål</h3>
 <p>
 Ett potentiellt kritiskt säkerhetshål har upptäckts i Windowsversionen av Bitcoin-QT. Om du kör Bitcoin-QT i någon av versionerna 0.5 t.o.m. 0.6 för Windows så bör du stänga av programmet och uppgradera till version 0.5.3.1 eller 0.6rc4 OMGÅENDE.
@ -226,7 +248,8 @@ href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/"
 href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/">
 0.5.3.1 för Windows och 0.5.3 för Linux</a>
 </p>
-
 <div style="text-align:right">
  <i>This notice last updated: Fri, 16 Mar 2012 22:58:00 UTC</i>
 </div>
+</div>
+
--- a/_alerts/2012-05-14-dos.html
+++ b/_alerts/2012-05-14-dos.html
@ -2,17 +2,23 @@
 title: "CVE-2012-2459: Critical Vulnerability (denial-of-service)"
 shorturl: "dos"
 active: false
+show_toc: true
 banner: ""
 date: 2012-05-14
 ---
-        <h2 id="risks">Risks</h2>
+
+<div class="post-content" markdown="1">
+<h2 id="risks">Risks</h2>
 <p>
 A denial-of-service vulnerability that affects all versions of
 bitcoind and Bitcoin-Qt has been reported and fixed. An attacker
 could isolate a victim's node and cause the creation of blockchain
 forks.
 </p>
-        <h2 id="solutions">Solutions</h2>
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">
+<h2 id="solutions">Solutions</h2>
 <p>
 Because this bug could be exploited to severely disrupt the Bitcoin
 network we consider this a critical vulnerability, and encourage
@ -22,7 +28,10 @@ everybody to upgrade to <a href="http://sourceforge.net/projects/bitcoin/files/B
 <a href="https://bitcointalk.org/?topic=79651">Backports for older releases (0.5.5 and 0.4.6) are also available</a> if
 you cannot upgrade to version 0.6.2.
 </p>
-        <h2 id="technical-details">Technical Details</h2>
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">
+<h2 id="technical-details">Technical Details</h2>
 <p>
 Full technical details are being withheld to give people the
 opportunity to upgrade.
@ -30,7 +39,10 @@ opportunity to upgrade.
 <p>
 Thanks to <a href="http://forre.st/">Forrest Voight</a> for discovering and reporting the vulnerability.
 </p>
-        <h2 id="questions-and-answers">Questions &amp; Answers</h2>
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">
+<h2 id="questions-and-answers">Questions &amp; Answers</h2>
 <h3 id="how-do-i-know">
 How would I know if I am the victim of this attack?
 </h3>
@ -64,3 +76,4 @@ No.
 <div style="text-align:right">
  <i>This notice last updated: Mon, 14 May 2012 17:00:00 UTC</i>
 </div>
+</div>
--- a/_alerts/2013-03-15-upgrade-deadline.html
+++ b/_alerts/2013-03-15-upgrade-deadline.html
@ -2,10 +2,13 @@
 title: "15 May 2013 Upgrade Deadline"
 shorturl: "may15"
 active: false
+show_toc: true
 banner: ""
 date: 2013-03-15
 ---
-        <h2 id="what-is-happening">What is happening</h2>
+
+<div class="post-content" markdown="1">
+<h2 id="what-is-happening">What is happening</h2>
 <p>
 If you are using an old version of Bitcoin-Qt (or bitcoind, the server bitcoin software),
 you must either upgrade to version 0.8.0 or later before May 15, 2013,
@ -25,13 +28,19 @@ We recommend that you
 before the 15th of May to avoid any issues.  If you are a solo miner or mining pool operator,
 please see the the notes at the end of this page for how to upgrade safely.
 </p>
-        <h2 id="backports">If you cannot upgrade to version 0.8.1</h2>
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">
+<h2 id="backports">If you cannot upgrade to version 0.8.1</h2>
 <p>
 If you cannot upgrade to the latest version,
 <a href="https://bitcointalk.org/?topic=199699">backports to older branches are now in final testing</a>.
 These include not only compatibility for the 15 May changes, but also fixes for known vulnerabilities and bugs, which have already been included and tested in the latest release.
 </p>
-        <h2 id="workaround">If you cannot upgrade to a backport</h2>
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">
+<h2 id="workaround">If you cannot upgrade to a backport</h2>
 <p>
 If you cannot upgrade to any of the above, you can still avoid the problem.
 Create a file called DB_CONFIG in the bitcoin data directory, containing this line:
@ -45,7 +54,10 @@ set_lk_max_locks 537000
 <a href="https://en.bitcoin.it/wiki/Data_directory">Look here</a> if you need help
 finding the bitcoin data directory.
 </p>
-        <h2 id="miners">Miners/mining pool operators</h2>
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">
+<h2 id="miners">Miners/mining pool operators</h2>
 <p>
 If you are creating new blocks (you are a solo miner or mining pool operator), then
 you should be aware that upgrading from 0.7 to 0.8 requires a lengthy
@ -59,7 +71,10 @@ reason, you should <b>not</b> set_lk_max_locks in a DB_CONFIG file until
 May 15th; if you increase locks before then you run the risk of creating
 or building on blocks incompatible with the rest of the network.
 </p>
-        <h2 id="why-necessary">Why this is necessary</h2>
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">
+<h2 id="why-necessary">Why this is necessary</h2>
 <p>
 A bug caused a <a href="/chainfork">temporary block chain fork on 11 March, 2013</a>.
 After investigating
@ -67,7 +82,7 @@ that bug, we determined that the bug can happen even if the entire network was
 still running old versions of Bitcoin-Qt/bitcoind. Therefore, the only option is to
 require everybody to either upgrade or workaround the bug.
 </p>
-
 <div style="text-align:right">
  <i>This notice last updated: Fri, 10 May 2013 21:30:00 UTC</i>
 </div>
+</div>
--- a/_alerts/2014-04-11-heartbleed.html
+++ b/_alerts/2014-04-11-heartbleed.html
@ -2,10 +2,13 @@
 title: "OpenSSL Heartbleed vulnerability"
 shorturl: "heartbleed"
 active: false
+show_toc: true
 banner: ""
 date: 2014-04-11
 ---

+<div class="post-content" markdown="1">
+
 <h2 id="what-happened">What happened</h2>
 
 <p>The version of OpenSSL used by Bitcoin Core software version 0.9.0 and earlier
@ -13,7 +16,9 @@ contains a bug that can reveal memory to a remote attacker. See
 <a href="http://heartbleed.com/">http://heartbleed.com/</a>
 for details.
 </p>
- 
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">
 <h2 id="what-you-should-do">What you should do</h2>
 
 <p>Immediately upgrade to <a href="/en/download">Bitcoin Core version 0.9.1</a> which is linked against
@ -32,7 +37,9 @@ Linux users should also upgrade their system's version of OpenSSL.
 <p>Android version 4.1.1 is vulnerable to Heartbleed. Try if you can upgrade to at
 least Android 4.1.2. If you are using Bitcoin Wallet on an Android phone, you
 should upgrade the app to at least version 3.45.</p>
- 
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">
 <h2 id="how-serious-is-the-risk">How serious is the risk</h2>
 
 <p>If you are using the Windows version of the Bitcoin Core GUI without a wallet
@ -50,3 +57,4 @@ very likely discover the rpcpassword and the last rpc request. It is possible
 <div style="text-align:right">
  <i>This notice last updated: Fri, 11 Apr 2014 12:19:23 -0400</i>
 </div>
+</div>
--- a/_alerts/2015-07-04-spv-mining.md
+++ b/_alerts/2015-07-04-spv-mining.md
@ -4,11 +4,15 @@

 title: "Some Miners Generating Invalid Blocks"
 shorturl: "spv-mining"
+show_toc: true
 active: false
 date: 2015-07-04
 #banner: "WARNING: many wallets currently vulnerable to double-spending of confirmed transactions (click here to read)"
 bannerclass: "alert"
 ---
+
+<div class="post-content" markdown="1">
+
 *This document is being updated as new information arrives.  Last
 update: 2015-07-15 13:00.  All times are UTC.*

@ -40,6 +44,9 @@ wallet is secured by Bitcoin Core 0.9.5 or later.
 - **Bitcoin Core 0.9.5 or later users are unaffected.**  (Note:
 [upgrade to 0.10.2][bitcoin core] is recommended due to
 denial-of-service vulnerabilities unrelated to this alert.)
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ##Miners

@ -48,7 +55,9 @@ blocks.  The Wiki Mining Pool Comparison page currently contains a list of [know
 suspected) good and bad pools][pool list].

 If you solo mine, please switch to Bitcoin Core 0.10.2.
+</div>

+<div class="toccontent-block boxexpand" markdown="1">
 <h2 id="solution">When Will Things Go Back To Normal?</h2>

 The problem is miners creating invalid blocks.  Some software can detect
@ -71,7 +80,9 @@ run and how they handle double spends, so unless you know for sure
 that they use Bitcoin Core 0.9.5 or later for full validation, you
 should assume they have the same security as the lightweight
 wallets described above.
+</div>

+<div class="toccontent-block boxexpand" markdown="1">
 <h2 id="cause">What's Happening</h2>

 Summary: Some miners are currently generating invalid blocks. Almost
@ -122,6 +133,9 @@ get all miners off of SPV mining and back to full validation (at
 least temporarily). If this happens, Bitcoin.org will reduce its
 current recommendation of waiting {{confs}} extra confirmations to a
 lower number.
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Updates

@ -131,6 +145,9 @@ strongest chain. See the recently-added [list of forks](#list-of-forks).
 Reports that the situation has passed are **not correct.** Please continue
 to wait {{confs}} more confirmations than you usually would wait before
 accepting a transaction.
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Invalid Blocks

@ -148,3 +165,4 @@ Please see the list of [invalid block hashes][] on the Bitcoin Wiki.
 [SPV]: http://bitcoin.stackexchange.com/questions/4649/what-is-an-spv-client
 [electrum note]: https://en.bitcoin.it/wiki/July_2015_Forks#Electrum
 [invalid block hashes]: https://en.bitcoin.it/wiki/July_2015_Forks#Invalid_Block_Hashes
+</div>
--- a/_alerts/2015-10-12-upnp-vulnerability.md
+++ b/_alerts/2015-10-12-upnp-vulnerability.md
@ -5,10 +5,13 @@
 title: "Vulnerability in UPnP library used by Bitcoin Core"
 shorturl: "upnp-vulnerability"
 active: false
+show_toc: true
 #banner: "WARNING: serious vulnerability in UPnP library used by Bitcoin Core (click here to read)"
 #bannerclass: "alert"
 ---

+<div class="post-content" markdown="1">
+
 ## Summary

 ![Disabling UPnP in the GUI](/img/alerts/disable_upnp.png)
@ -23,6 +26,9 @@ Also upgrade to a version of Bitcoin Core at least [0.10.3](https://bitcoin.org/
 or [0.11.1](https://bitcoin.org/en/download). These versions upgrade the
 library to a non-vulnerable version, as well as disable UPnP by default to
 prevent this problem in the future.
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Details

@ -46,6 +52,9 @@ by default, unless `--enable-upnp-default` was provided to the configure script.

 Releases starting from 0.10.3 and 0.11.1, and the upcoming 0.12.0 will still ship
 with (a patched version) of the library, but no longer enable the functionality by default.
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Mitigation

@ -54,6 +63,9 @@ Stack Smashing Protection (SSP), and non-executable stack and heap (DEP) enabled
 makes it harder to use this vulnerability for remote code execution or private
 key leaks. However, it is still advised to upgrade, or if not possible, disable
 UPnP as soon as possible.
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Manual Port Forwarding

@ -63,3 +75,4 @@ will not accept incomming connections from other peers unless you
 manually enable port forwarding on your router.  If you wish to do
 that---it isn't required---please [follow these
 instructions](/en/full-node#network-configuration).
+</div>
--- a/_alerts/2016-08-17-binary-safety.md
+++ b/_alerts/2016-08-17-binary-safety.md
@ -8,6 +8,8 @@ active: false
 banner: ""
 ---

+<div class="post-content" markdown="1">
+
 ## Summary

 Bitcoin.org has reason to suspect that the binaries for the upcoming Bitcoin Core release will likely be targeted by
@ -26,3 +28,4 @@ The hashes of Bitcoin Core binaries are cryptographically signed with [this key]
 We strongly recommend that you download Wladimir's key from multiple sources in addition to Bitcoin.org for comparison purposes. For example, you can cross reference Bitcoin.org's copy with the [bitcoin-dev mailing list](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-June/009045.html) where Wladimir signed a message containing the key's fingerprint (01EA5486DE18A882D4C2684590C8019E36C2E964), but we encourage you to seek out other sources as well in order to make sure you are verifying your download with the correct key. Furthermore, we recommend verifying your download using signatures from multiple developers using the gitian signatures repository.

 It is always best practice to securely verify multiple signatures and hashes before running any Bitcoin Core binaries. This is the safest and most secure way to ensure that the binaries you're running are the same ones created by the Core Developers.
+</div>
--- a/_alerts/2016-11-01-alert-retirement.md
+++ b/_alerts/2016-11-01-alert-retirement.md
@ -5,10 +5,14 @@
 title: "Alert System Retirement"
 shorturl: "alert-retirement"
 active: false
+show_toc: true
+
 ## banner: "Alert system is being retired (click here to read)"
 ## bannerclass: "info"
 ---

+<div class="post-content" markdown="1">
+
 ## Updates

 * **January 19, 2017**: The Final alert has been broadcast. This final alert essentially disables the alert system by overriding all
@ -16,12 +20,17 @@ alerts, preventing other alerts from being broadcast, and displays the static me
 will be published in the coming months.
 * **March 8, 2017**: Bitcoin Core 0.14 released with hard-coded [final alert](https://bitcoin.org/en/release/v0.14.0#final-alert).
 * **May 1, 2017**: Postpone release date of Alert key. Older clients may contain Alert handling code which is exploitable using the alert key, therefore the public release of the key has been temporarily postponed until considered safe.
+</div>

+<div class="toccontent-block boxexpand" markdown="1">

 ## Summary

 The network wide Alert system is being retired. **_No Bitcoins are at risk and this warning may be safely ignored._**
 Upgrade to the newest version of your wallet software to no longer see the alert.
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Reasons for Retirement

@ -40,6 +49,9 @@ not be imposed on the entire network.

 The Alert system has also lost its usefulness. It is no longer necessary to use it to inform users about problematic network
 events as users can easily get their information from any major Bitcoin news outlet.
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## The Retirement Plan

@ -54,6 +66,9 @@ receive the final alert.
 |Pre-final Alert|The alert itself warning that the Alert system will be retired|2016-11-02|
 |Final Alert|Max sequence Alert to disable the Alert system|2017-01-19|
 |Alert key release|The Alert key will be made publicly available|Postponed until further notice.|
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Software without the Alert system

@ -63,6 +78,9 @@ are guaranteed to have removed/disabled the Alert system or allow you to disable
 * Bitcoin Core 0.12.1+
 * Bitcoin Core 0.10.3, 0.11.x, and 0.12.x can disable alerts with `-alerts=0`
 * Armory 0.94.1+
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## See also

@ -71,3 +89,4 @@ are guaranteed to have removed/disabled the Alert system or allow you to disable
 * [Removal discussion on github](https://github.com/bitcoin/bitcoin/pull/6260)
 * [Pull request disabling alerts](https://github.com/bitcoin/bitcoin/pull/6274)
 * [IRC Discussion](https://botbot.me/freenode/bitcoin-core-dev/2016-09-22/?msg=73446303&page=6)
+</div>
--- a/_alerts/2017-07-12-potential-split.md
+++ b/_alerts/2017-07-12-potential-split.md
@ -5,9 +5,13 @@
 title: "Potential network disruption"
 shorturl: "potential-split"
 active: false
+show_toc: true
 ## banner: "Warning: wait for extra confirmations starting July 22nd"
 ## bannerclass: "warning"
 ---
+
+<div class="post-content" markdown="1">
+
 {% assign start='<span class="date">2017/08/01 00:00 UTC</span>' %}

 *Last updated: <span class="date">2017/07/21 12:00 UTC</span>.  This
@ -27,6 +31,9 @@ We also recommend monitoring this page and other Bitcoin news sites for
 additional information and updates.

 *Outdated information from earlier versions of this post follows.*
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Chain split

@ -69,6 +76,9 @@ the operators or contributors to this website can do to help you.
 *Note:* there is a chance a milder level of disruption could start
 between now and {{start}}.  If that is the case, this post will be
 updated with details.
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Preparation

@ -90,6 +100,9 @@ give you your bitcoins on versions they don't like.
 1. Bitcoin may experience significant price fluctuations in relation to
 other currencies.  Learn more about [price volatility][] and ensure you
 aren't holding more bitcoin than you can afford to lose.
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## During the event

@ -106,6 +119,9 @@ recipient at your expense.
 1. Be wary of offers to allow you to invest in the outcome of the event
 by "splitting" your coins.  Some of these offers may be scams, and
 software claiming to split your coins can also steal them.
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## After the event

@ -113,6 +129,9 @@ We will update this section with more information after {{start}}.  Please
 monitor this page accordingly and wait until multiple news sources that you
 trust have stated that the event is resolved before returning to normal Bitcoin
 use.
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Document history

@ -135,6 +154,7 @@ first.
 [community resources]: /en/community
 [confirmation scoring]: /en/you-need-to-know#instant
 [price volatility]: /en/you-need-to-know#volatile
+</div>

 <script src="/js/jquery/jquery-1.11.2.min.js"></script>
 <script>
--- a/_alerts/2017-10-09-segwit2x-safety.md
+++ b/_alerts/2017-10-09-segwit2x-safety.md
@ -2,11 +2,14 @@
 title: "Beware of Bitcoin's possible incompatibility with some major services"
 shorturl: "segwit2x-safety"
 active: false
+show_toc: true
 ## banner: "Beware of Bitcoin's possible incompatibility with some major services"
 ## bannerclass: "alert"
 date: 2017-10-11
 ---

+<div class="post-content" markdown="1">
+
 ## Summary

 A subsection of the Bitcoin economy including prominent businesses such as Coinbase, Xapo, and BitPay have signed an agreement to adopt
@ -29,6 +32,9 @@ However users should only use these wallets to store their coins and never perfo
 make on the Bitcoin blockchain can also be replicated and "replayed" on the altcoin chain. If the coins on the contentious
 hard fork have any value, there will be methods you can use to "split" your coins and have access to them. Pay extra attention
 to major Bitcoin communication channels and media shortly after the fork so you stay informed.
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Mobile wallets

@ -44,6 +50,9 @@ to support the hard fork, it is safe to continue using mobile wallets, however y
 sources of Bitcoin news such as this website, [/r/bitcoin](https://www.reddit.com/r/Bitcoin/), and the [Bitcoin Forum](https://bitcointalk.org)
 to make sure that it's safe to continue using your particular wallet. As a general rule, you should not perform any transactions
 during and shortly after the hard fork.
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## After the fork

@ -68,6 +77,9 @@ this altcoin as "Bitcoin" or "BTC" to their users after the hard fork. These ser
 the Bitcoin system in a contentious manner and therefore are no longer useful to our visitors.

 The following companies and services have pledged to adopt the contentious hard fork:
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Wallets

@ -86,6 +98,9 @@ The following companies and services have pledged to adopt the contentious hard
 + Ripio (Argentina)
 + Unocoin (India)
 + **Xapo (United States)**
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Exchanges

@ -102,6 +117,9 @@ The following companies and services have pledged to adopt the contentious hard
 + Safello (Sweden)
 + SFOX (United States)
 + **ShapeShift (Switzerland)**
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Miners

@ -112,6 +130,9 @@ The following companies and services have pledged to adopt the contentious hard
 + Bixin.com (China)
 + Genesis Mining (Hong Kong)
 + ViaBTC (China)
+</div>
+
+<div class="toccontent-block boxexpand" markdown="1">

 ## Other

@ -129,3 +150,4 @@ The following companies and services have pledged to adopt the contentious hard
 + Netki (United States)
 + Purse (United States)
 + Veem (United States)
+</div>
--- a/_layouts/alert.html
+++ b/_layouts/alert.html
@ -3,6 +3,10 @@
 # http://opensource.org/licenses/MIT.

 layout: base
+end_of_page: |
+  <script>updateToc();</script>
+  <script>boxShow();</script>
+  <script>onScrollButton();</script>
 ## Note: global variables like page.lang must be set in _config.yml for collections
 ---
 {% if page.canonical != nil %}
@ -13,20 +17,49 @@ layout: base
 <link rel="alternate" type="application/rss+xml" href="/en/rss/alerts.rss" title="Bitcoin network status and alerts">

 <div class="subhead-links">
-  <a href="/en/alerts">Network alerts history</a>
-| <a type="application/rss+xml" href="/en/rss/alerts.rss"><img src="/img/icons/header_rss.svg" alt="rss" class="rssicon"> Subscribe to RSS feed</a>
-| <a href="https://github.com/bitcoin-dot-org/bitcoin.org/commits/master/{{page.path|uri_escape}}">Post history</a>
-| <a href="https://github.com/bitcoin-dot-org/bitcoin.org/issues/new?body=Source%20File%3A%20{{page.path|uri_escape}}%0A%0A">Report issue</a>
+  <div class="container">
+    <a href="/en/alerts">Network alerts history</a>
+    |
+    <a type="application/rss+xml" href="/en/rss/alerts.rss">
+      <img src="/img/icons/header_rss.svg" alt="rss" class="rssicon"> Subscribe to RSS feed</a>
+    |
+    <a href="https://github.com/bitcoin-dot-org/bitcoin.org/commits/master/{{page.path|uri_escape}}">Post history</a>
+    |
+    <a href="https://github.com/bitcoin-dot-org/bitcoin.org/issues/new?body=Source%20File%3A%20{{page.path|uri_escape}}%0A%0A">Report issue</a>
+  </div>
 </div>

-<div class="post">
-
-  <header class="post-header">
-    <h1 class="post-title alerttitle"><img src="/img/icons/warning.svg" alt="warning">{{ page.title }}<br><small>{{ page.date | date:"%e %B %Y" }}</small></h1>
-  </header>
-
-  <article class="post-content">
-    {{ content }}
-  </article>

+<div class="hero">
+  <div class="container">
+      <h1 class="post-title alerttitle">{{ page.title }}</h1>
+      <p class="summary">{{ page.date | date:"%e %B %Y" }}</p>
+  </div>
 </div>
+
+<div class="toc-container">
+  <div class="row toc-row">
+    {% if page.show_toc %}
+    <div id="toc" class="toc">
+      <div>
+        <button class="mob-sidebar-open" hidden>ALL TOPICS</button>
+        <div class="sidebar">
+          <div class="sidebar-inner" markdown="1">
+            <button class="mob-sidebar-close" hidden></button>
+            {% include helpers/toc.html html=content %}
+          </div>
+        </div>
+      </div>
+    </div>
+    {% endif %}
+
+    <div class="toccontent">
+      <article class="article">
+        {{ content }}
+      </article>
+    </div>
+
+  </div>
+</div>
+  
+
--- a/_layouts/post.html
+++ b/_layouts/post.html
@ -31,11 +31,11 @@ end_of_page: |
  </div>
 </header>

-<div class="container">
+<div class="toc-container">
  <div class="row toc-row">
  {% if page.show_toc %}
-    <div markdown="1" id="toc" class="toc">
-      <div markdown="1">
+    <div id="toc" class="toc">
+      <div>
        <button class="mob-sidebar-open" hidden>ALL TOPICS</button>
        <div class="sidebar">
          <div class="sidebar-inner" markdown="1">
@ -47,8 +47,8 @@ end_of_page: |
    </div>
  {% endif %}

-    <div markdown="1" class="toccontent">
-      <article class="article">
+    <div class="toccontent">
+      <article class="article" markdown="1">
        {{ content }}
        <p class="post-meta">Posted to the
        <a href="/en/blog">Bitcoin.org Site Blog</a> on {{ page.date | date: "%d %B %Y" }} {% if page.author %} by {{ page.author }}{% endif
--- a/_sass/screen.scss
+++ b/_sass/screen.scss
@ -1600,12 +1600,6 @@ div.one-column {
 .one-column th {
        text-align: center;
 }
-
-// div.post {
-//         max-width: 40em;
-//         margin-right: auto;
-//         margin-left: auto;
-// }
 .article img {
    max-width: 100%;
 }
@ -3934,6 +3928,10 @@ button.active {
    .toc+.toccontent {
        border: none;
    }
+    .toccontent .toccontent-block {
+        padding-left:0;
+        padding-right:0;
+    }
    .toccontent-block {
        border-top: none;
        margin-bottom: 2px;
@ -3947,6 +3945,10 @@ button.active {
    .toccontent .subhead-links a:not(:first-child) {
        margin-left: 2px;
    }
+    .article>* {
+        padding-left:15px;
+        padding-right:15px;
+    }
    .dev-documentation {
        padding: 30px 0 50px;
    }
@ -4046,7 +4048,7 @@ button.active {
        width: 100%;
    }
    .post-content {
-        padding: 0 0 30px;
+        padding-bottom: 30px;
    }
 }