Skip to content

Commit

Permalink
* Adding new minor release.
Browse files Browse the repository at this point in the history
* Adding rationale to the verification process page.
* Other minor
  • Loading branch information
fresheneesz committed Jun 15, 2020
1 parent 443c5d4 commit a03b69d
Show file tree
Hide file tree
Showing 5 changed files with 14 additions and 4 deletions.
Binary file removed Clipboard02.png
Binary file not shown.
10 changes: 8 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

# Tordl Wallet Protocols

**Version:** 0.4.0, **Status:** *Ready for Review*
**Version:** 0.4.1, **Status:** *Ready for Review*

The Tordl Wallet protocols are step-by-step guides for storing bitcoins in a secure self-managed be-your-own-bank way. There are a number of methods, each with their own trade offs. Some of the methods are able to securely store large amounts of money ($100,000+) for the long term. Following these protocols can give you the peace of mind that your funds are safe and can be accessed relatively easily when needed.

Expand Down Expand Up @@ -118,7 +118,13 @@ All information in this repository is for general informational purposes only an

## Release Notes

* v0.4 - First Release
* v0.4.1 (Unreleased)
* Errata: None.
* Upgrade Guidance: No changes needed.
* Other Changes:
* Improved recovery steps
* Releases will now contain html rather than markdown files.
* v0.4.0 - First Release
* Errata: N/A
* Upgrade Guidance: N/A
* Other Changes: N/A
5 changes: 4 additions & 1 deletion generate-release.js
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,10 @@ var marked = require("marked")
var fwalk = require('kc-fwalk')

var newReleaseDirName = "new-release"
var ignoreDirectories = [".", "node_modules", "releases", "generate-release.js", "yarn.lock", newReleaseDirName]
var ignoreDirectories = [
".", "node_modules", "releases", "generate-release.js", "yarn.lock", "tordlWalletProtocols.iml",
"package.json", newReleaseDirName
]

;(async function() {
try {
Expand Down
1 change: 1 addition & 0 deletions misc/obtaining-tordl.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,4 +27,5 @@ This page goes over how to obtain and verify a release of the Tordl Wallet Proto

## Rationale

* This process of obtaining and verifying the actual release, rather than simply using the guide directly from github, is important so as to prevent potential thieves from feeding you insecure advice they can then exploit to steal your coins. It is always important to verify the validity of security focused software and how-to information. If you go through this process of validation, it ensures that there is no intentionally malicious information in the guide unless it comes directly from the creator of the protocol (the person who signed the release).
* `fresheneesz's public key` is not included in the release bundle because it makes it harder for a malicious actor to trick people into downloading an inauthentic malicious version of the release. Both the github and keybase accounts would have to be compromised for an inauthentic release to validate using this guide.
2 changes: 1 addition & 1 deletion misc/protocol-updates.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

1. Check for new protocol releases at https://github.com/fresheneesz/TordlWalletProtocols/releases.
2. If there is a newer release, download the newest release.
3. In the main `README.md` file in the *Release Notes* section, check the protocol errata (a log of errors in previous versions) for all the versions since the last time you ran through this process (or if this is the first time, for all versions after the version your wallet uses, which is recorded in your `unencrypted Digital Data Record`).
3. In the main `README.html` file in the *Release Notes* section, check the protocol errata (a log of errors in previous versions) for all the versions since the last time you ran through this process (or if this is the first time, for all versions after the version your wallet uses, which is recorded in your `unencrypted Digital Data Record`).
4. Make any necessary corrections based on those errata. Any recommendations are prominently mentioned at the top of the notes for each version.
5. If you want to upgrade, check the *Upgrade Guidance* section for each of the versions you checked in step 3.

Expand Down

0 comments on commit a03b69d

Please sign in to comment.