mirror of
https://github.com/seigler/dash-docs
synced 2025-07-28 10:16:15 +00:00
7d98f798ab
Gemfile:
- Upgrade to Jekyll 3.x (3.0.1 tested). This brings several new
features I want to use, most notably *collections* which allows us
to add blog-like collections. I've converted the `_releases` and
`_alerts` pages into collections, although their plugins are
maintained to handle the Download and Active Alert features.
- Upgrade to latest Kramdown.
- Lock Less at 2.4.0. This prevents breaking our Less plugin. Jekyll
3.x provides native support for SCSS, so we may want to switch to
that in time.
- Lock HTML Proofer at 2.1.0. The most recent version was taking
forever to check our pages (I never actually got it to complete).
I'll look into it when I get more time.
Makefile:
- New `make clean` command. Jekyll 3.x by default attempts to do
incremental rebuilds. The new `jekyll clean` command cleans up the
metadata necessary for than so that a full build is performed, and
this new `make clean` command is a wrapper around it so that we
automatically do full rebuilds in the relevant cases. Note: our
plugins aren't fully compatible with the incremental rebuilds, but
I'd like to fix that in the future.
- Remove WEBrick hack to enable previewing with default URL paths (/
instead of /index.html).
- Filter out compliants from Rouge
README.md:
- Now that Alerts (_alerts) are part of a collection, the file names
are no longer parsed for dates, so instructions on adding the date
to the YAML metadata have been added.
_alerts/*:
- Now that alerts are part of a collection, the file names are no
longer parsed to provide dates, so a `date:` field has been added to
the YAML metadata.
_config.yml:
- Some variables renamed per upgrade instructions.
- Switched from old default syntax highlighter Pygments to new default
Rouge. I tried to use Rouge options to keep new output as similar
to old output as possible to making diffing easy, but Rouge adds
extra CSS class info.
- Move `_alerts` and `_releases` into Jekyll 3.x "collections", which
provide the organizational features we were using plugins to
manange. I haven't removed the old plugins because we still use
some of their features (alerts.rb provides active issue and banner
features; releases.rb provides info to Download page)
- _layouts/* can no longer provide default global metadata; that is now
provided in the new `defaults:` section in _config.yml.
_layouts/*:
- Default metadata can no longer be provided in the layout files for
collections, so I've removed it and left a message to see
_config.yml.
_plugins/*:
- Remove filter_for.rb. It's completely broken on Jekyll 3.x because
of changes to Liquid which prevent adding new arguments to the
inherited Liquid::For class. Existing uses of filter_for have been
migrated to built-in for loops prefaced by sorts.
- Remove remove-html-extension.rb: at it said in the comments, this
was a temporary hack to get us to Jekyll 3.0.
_releases/*:
- Rename all the files: prefix a v to the file name so the output html
(e.g. v10.0.0.html) is the same as the source filename (e.g.
v10.0.0.md). This is necessary to migrate them to a Jekyll collection.
- Remove %v from titles: we have to explicitly set the title, like we
used to. Again required for migration to collections.
_templates/events.html & en/rss/events.rss:
- Sort events by date and then loop with regular for loop rather than
filter_for
en/alerts.html & en/rss/alerts.rss:
- Sort alerts by date and then loop with regular for loop rather than
filter_for
en/bitcoin-core/index.md & en/version-history.html & en/rss/releases.rss:
- Sort alerts by date and then loop with regular for loop rather than
filter_for
84 lines
4 KiB
Markdown
84 lines
4 KiB
Markdown
---
|
|
# This file is licensed under the MIT License (MIT) available on
|
|
# http://opensource.org/licenses/MIT.
|
|
# Text originally from Bitcoin Core project
|
|
# Metadata and small formatting changes from Bitcoin.org project
|
|
|
|
## Please see _releases/0.10.0.md for a release template
|
|
required_version: 0.4.0
|
|
optional_date: 2011-09-23
|
|
title: Bitcoin version 0.4.0 released
|
|
---
|
|
[Full announcement (including signatures)](http://sourceforge.net/mailarchive/message.php?msg_id=28132490)
|
|
|
|
Bitcoin version 0.4.0 is now available for download at:
|
|
<http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.0/>
|
|
|
|
The main feature in this release is wallet private key encryption;
|
|
you can set a passphrase that must be entered before sending coins.
|
|
See below for more information; if you decide to encrypt your wallet,
|
|
**WRITE DOWN YOUR PASSPHRASE AND PUT IT IN A SECURE LOCATION**. If you
|
|
forget or lose your wallet passphrase, you lose your bitcoins.
|
|
Previous versions of bitcoin are unable to read encrypted wallets,
|
|
and will crash on startup if the wallet is encrypted.
|
|
|
|
Also note: bitcoin version 0.4 uses a newer version of Berkeley DB
|
|
(bdb version 4.8) than previous versions (bdb 4.7). If you upgrade
|
|
to version 0.4 and then revert back to an earlier version of bitcoin
|
|
the it may be unable to start because bdb 4.7 cannot read bdb 4.8
|
|
"log" files.
|
|
|
|
Notable bug fixes from version 0.3.24
|
|
-------------------------------------
|
|
|
|
* Fix several bitcoin-becomes-unresponsive bugs due to multithreading
|
|
deadlocks.
|
|
|
|
* Optimize database writes for large (lots of inputs) transactions
|
|
(fixes a potential denial-of-service attack)
|
|
|
|
|
|
|
|
Wallet Encryption
|
|
-----------------
|
|
Bitcoin supports native wallet encryption so that people who steal your
|
|
wallet file don't automatically get access to all of your Bitcoins.
|
|
In order to enable this feature, chose "Encrypt Wallet" from the
|
|
Options menu. You will be prompted to enter a passphrase, which
|
|
will be used as the key to encrypt your wallet and will be needed
|
|
every time you wish to send Bitcoins. If you lose this passphrase,
|
|
you will lose access to spend all of the bitcoins in your wallet,
|
|
no one, not even the Bitcoin developers can recover your Bitcoins.
|
|
This means you are responsible for your own security, store your
|
|
passphrase in a secure location and do not forget it.
|
|
|
|
Remember that the encryption built into bitcoin only encrypts the
|
|
actual keys which are required to send your bitcoins, not the full
|
|
wallet. This means that someone who steals your wallet file will
|
|
be able to see all the addresses which belong to you, as well as the
|
|
relevant transactions, you are only protected from someone spending
|
|
your coins.
|
|
|
|
It is recommended that you backup your wallet file before you
|
|
encrypt your wallet. To do this, close the Bitcoin client and
|
|
copy the wallet.dat file from ```~/.bitcoin/``` on Linux, ```/Users/(user
|
|
name)/Library/Application Support/Bitcoin/``` on Mac OSX, and ```%APPDATA%/Bitcoin/```
|
|
on Windows (that is ```/Users/(user name)/AppData/Roaming/Bitcoin``` on
|
|
Windows Vista and 7 and ```/Documents and Settings/(user name)/Application
|
|
Data/Bitcoin``` on Windows XP). Once you have copied that file to a
|
|
safe location, reopen the Bitcoin client and Encrypt your wallet.
|
|
If everything goes fine, delete the backup and enjoy your encrypted
|
|
wallet. Note that once you encrypt your wallet, you will never be
|
|
able to go back to a version of the Bitcoin client older than 0.4.
|
|
|
|
Keep in mind that you are always responsible for your own security.
|
|
All it takes is a slightly more advanced wallet-stealing trojan which
|
|
installs a keylogger to steal your wallet passphrase as you enter it
|
|
in addition to your wallet file and you have lost all your Bitcoins.
|
|
Wallet encryption cannot keep you safe if you do not practice
|
|
good security, such as running up-to-date antivirus software, only
|
|
entering your wallet passphrase in the Bitcoin client and using the
|
|
same passphrase only as your wallet passphrase.
|
|
|
|
See the ```doc/README``` file in the bitcoin source for technical details
|
|
of wallet encryption.
|