Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updating docs #384

Merged
merged 1 commit into from
Oct 6, 2017
Merged

updating docs #384

merged 1 commit into from
Oct 6, 2017

Conversation

Zamiell
Copy link
Contributor

@Zamiell Zamiell commented Oct 6, 2017

No description provided.

@@ -27,9 +27,9 @@ The slightly more awesome Standard Unix Password Manager for Teams. Written in G

> Password management should be simple and follow [Unix philosophy](http://en.wikipedia.org/wiki/Unix_philosophy). With `pass`, each secret lives inside of a `gpg` encrypted file whose filename is the title of the website or resource that requires the secret. These encrypted files may be organized into meaningful folder hierarchies, copied from computer to computer, and, in general, manipulated using standard command line file management utilities. - [passwordstore.org](https://www.passwordstore.org/)

`gopass` is a rewrite of `pass` in [Go](https://golang.org/) with the aim of making it cross-platform and [adding additional features](#features). Our target audience are professional developers and sysadmins (and especially teams of those) who are well versed with a command line interface. One explicit goal for this project is to make it more approachable to non-technical users. We go by the UNIX philosophy and try to do one thing and do it well, providing a stellar user experience and a sane, simple interface.
*gopass* is a rewrite of the *pass* password manager in [Go](https://golang.org/) with the aim of making it cross-platform and [adding additional features](#features). Our target audience are professional developers and sysadmins (and especially teams of those) who are well versed with a command line interface. One explicit goal for this project is to make it more approachable to non-technical users. We go by the UNIX philosophy and try to do one thing and do it well, providing a stellar user experience and a sane, simple interface.
Copy link
Contributor Author

@Zamiell Zamiell Oct 6, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here, I begin the work of standardizing stylization of gopass to not use backticks

@@ -1,28 +0,0 @@
# Known Limitations and Caveats
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is combined with the security section; i think it makes more sense that way

If a config exists it will attempt to parse and load the settings. If this
fails program execution aborts. If `gopass` can not start because of broken
or incompatible config file move it away (make a backup) and start fresh.
During startup, gopass will look for a configuration file at `$HOME/.config/gopass/config.yml`. If one is not present, it will create one. If the config file already exists, it will attempt to parse it and load the settings. If this fails, the program will abort. Thus, if gopass is giving you trouble with a broken or incompatible configuration file, simply rename it or delete it.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

having the default config location here is obviously a must

@@ -2,11 +2,44 @@

## Standard Features

### Data Organization
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this section was in setup.md, which was a mistake. i migrated it here and fleshed it out

@@ -89,18 +122,15 @@ The generated password for golang.org/gopher is:
Eech4ahRoy2oowi0ohl
```

The `generate` command will ask for any missing arguments, like the name of the
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Standardization of no line breaks style here, as well as in other places


### Ultimate Goals of Security
## Security Goals
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rewrote this so that it matches CIA/NP triad

name of the secrets.
* **Integrity** - Ensure that only authorized parties are allowed to modify data.
* gopass makes no attempt at protecting the integrity of a store. However, we plan to do this in the future.
* **Availability** - Secrets must always be readable by exactly the specified recipients.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added a note here on availability

@@ -71,25 +70,11 @@ Now, you have created a public and private key pair. If you don't know what that
* ["git + gpg, know thy commits" at coderwall](https://coderwall.com/p/d3uo3w/git-gpg-know-thy-commits)
* ["Generating a new GPG key" by GitHub](https://help.github.com/articles/generating-a-new-gpg-key/)

### Securing Your Editor
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

moved to post installation steps

@dominikschulz dominikschulz self-requested a review October 6, 2017 16:14
@dominikschulz dominikschulz added this to the 1.5.0 - Wizards milestone Oct 6, 2017
Copy link
Member

@dominikschulz dominikschulz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much. These are invaluable contributions. You clearly have a grip for writing and style!

@dominikschulz dominikschulz merged commit 97a5c36 into gopasspw:master Oct 6, 2017
kpitt pushed a commit to kpitt/gopass that referenced this pull request Jul 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants