Back In Time VS pass-import

it is often asked by beginners how and where starting to contribute. As member of the maintenance team of Back In Time (Backup software using rsync in the back, written with Python and Qt) I would like to introduce one of our "good first issues" (#1578).

I'm member of the upstream maintenance team of Back In Time a rsync-based backup software. No one gets payed. No company behind hit. Even the maintainers and developers are volunteers.

Back In Time is a round about 15 years old backup software using rsync in the back. I'm part of the 3rd generation maintenance team there. A lot of work in investigating and fixing issues, understanding, documenting and refactoring old code.

This request is related to an Open Source project named Back In Time. Everyone there works voluntarily and unpaid.

In my own project we do it more transparent. We close if there is a good reason for it. We don't close just because no one is working on something. If there are no resources to work in it now but it seems important we keep it open until it is fixed. We do use milestones and priority labels to give the users an idea about our plans.

I'm member of the maintenance team of Back In Time a rsync-based backup software.

Most of the strings are form two past developers (the founder and the past maintainer). Since last summer we took over the project and try to clean things up. Some of the source strings just got a review from a linguist and he also mentioned about that exclamation marks. But he kind of stopped at some point because it was to much. ;)

Currently the translation is locked because of maintenance issues and an open PR offering review of original English strings.

Great and thanks. Feel free to ask further questions in the Issues section of our project or the bit-dev.python.org mailing list. Of course you can contact me directly here.

I'm interested in that topic because I'm member of the maintenance team of Back In Time, the software discussed in that video. The version in video is 0.9, today Back In Time reached 1.3.3. Also interesting is that I'm the third generation of maintainers to that project. I'm not sure but 0.9 there was the fist maintainer and founder involved only.

> I always tell these people to just sign up for a password manager and they always resist and say no. I must be missing something obvious.

Maybe they don't want to be relying on a random third-party for all their passwords?

Rather than getting them to sign up for a password manager, what about getting them to install a password manager? I use https://www.passwordstore.org/ - it encrypts your passwords with GPG, and shares the storage via a Git repository for synchronisation between different machines.

That way you can delegate the password handling to another program, e.g. a password manager like pass(1) (https://www.passwordstore.org/) or some interactive graphical prompt.

I want to move to something compatible with https://www.passwordstore.org/ - an open standard for keeping your passwords in a folder encrypted with OpenPGP.

The problem is that I'm nervous to give an unknown Android app and browser plugin total control of my passwords and access to my github account when I don't have time to review it's code properly. I have a bit more trust ing the command line tools, but I'd like to be sure that more people are looking at the code before I trust my life to it.

> Create a system or pattern based on url or brand and mentally hash it into a password.

Doesn't sound very secure. Also when you realize that you anyway have to trust cryptography, I believe it starts making a lot of sense to have an actual cryptographic key and encrypt it with one good random password you learn by heart.

I use pass https://www.passwordstore.org/, which encrypts my passwords with my GPG key, which comes from my Yubikey, which I unlock with a password. That means that I only need to remember one password, and it feels a lot more secure than your pattern based on url or brand.

i use pass and keep my database on a local git repo. it encrypts your passwords with gpg and is a really simple command line program

If you want portability and simplicity, there's a project called simply pass that uses standard *nix utilities (and git, I believe) to manage passwords from CLI.

0. Pass is just text files encrypted with gpg. I needed just one password on one work computer, where I had my gpg key, but not all my passwords. Decrypted the file and that was it.

1. There are plugins and web clients: https://www.passwordstore.org/#extensions

I've been incredibly happy with https://www.passwordstore.org/ for years. The data store is a file hierarchy, with the files themselves encrypted with GPG. Sync is via git. TOTP support with a plugin.