Commit graph

5 commits

Author SHA1 Message Date
Steve Wills
1fb57dc568 - Update to 1.4.2
PR:		ports/172916
Submitted by:	milki <milki@rescomp.berkeley.edu> (maintainer)
Feature safe:	yes
2012-10-21 04:14:32 +00:00
Steve Wills
6c8f6e451a - Add missing bash depends
PR:		ports/172126
Submitted by:	milki <milki@rescomp.berkeley.edu> (maintainer)
2012-09-29 13:27:07 +00:00
Steve Wills
0807da6587 - Fix build on 7.x
PR:		ports/171927
Submitted by:	milki <milki@rescomp.berkeley.edu> (maintainer)
2012-09-27 13:30:59 +00:00
Steve Wills
e9b9700f2c - Update to 1.4
- Patches updated

PR:		ports/171905
Submitted by:	milki <milki@rescomp.berkeley.edu> (maintainer)
2012-09-24 14:04:31 +00:00
Steve Wills
ecd8106d7f Password management should be simple and follow Unix philosophy. With pass, each
password lives inside of a gpg encrypted file whose filename is the title of the
website or resource that requires the password. 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.

pass makes managing these individual password files extremely easy. All
passwords live in ~/.password-store, and pass provides some nice commands for
adding, editing, generating, and retrieving passwords. It is a very short and
simple shell script. It's capable of temporarily putting passwords on your
clipboard and tracking password changes using git.

You can edit the password store using ordinary unix shell commands alongside the
pass command. There are no funky file formats or new paradigms to learn. There
is bash completion so that you can simply hit tab to fill in names.

WWW: http://zx2c4.com/projects/password-store/

PR:		ports/171686
Submitted by:	milki@rescomp.berkeley.edu
2012-09-17 02:37:38 +00:00