Re: [orca-list] Which password managers do you use with orca?
- From: Matt Dizak <matt dizak gmail com>
- To: Alexander Epaneshnikov <aarnaarn2 gmail com>
- Cc: orca-list <orca-list gnome org>
- Subject: Re: [orca-list] Which password managers do you use with orca?
- Date: Thu, 18 Nov 2021 16:03:57 -0800
I've been having the same issues myself with Keepassx/2 and others.
So figured I'd quickly write out a password manager as a CLI tool in
Python, and open source it.
Not sure how to go about implementation though, and any input would be
greatly appreciated. Three different methods I can think of:
1.) Run the program, get prompted for your encryption password, and
remain in a presistent connected state to the program. Simple menu
such as "1 <site_alias>" to copy password to your clipboard, "2" to
list saved passwords, "3" to add a new password, et al. Once you exit
the program, database is locked and to gain a password again you need
to open the program and enter your encryption password again.
Viturally, same as folks like Keepass have things setup.
2.) I don't personally like #1 though, as that means I have to have
one terminal window constantly open dedicated to keeping that CLI tool
running. I prefer CLI tools that don't put you into a persisent
state. One option is 4096 bit RSA keys plus ssh-agent. When you
first login to your computer, add the ssh key to ssh-agent, and
optionally enter the key's password. That private key is now in
memory for the duration of your session, and you can just run commands
from the terminal prompt like:
blindpass copy <site_alias> -- Password will then be in your clipboard
blindpass add <site_alias> <password>
blindpass list
And so on. Each time you run a command, it'll use the RSA private key
stored within ssh-agent to decrypt necessary part of the database and
provide your password.
3.) Problem with #2 is your passwords are available at al times during
your computer session. Another option is use the encryption password
as in #1 instead of RSA private keys, bu while keeping the simplicity
of #2, but add a timer to how long the password database will be open
for. When you run a 'blindpass' command in terminal, if the database
is closed, it'll ask for your encryption password and how long you'd
like to keep it open for. From there, the simplistic commands such as
#2 will work for that time period.
I don't know, but spitting out thoughts here. Any input would be appreciated.
Thanks,
Matt
On 11/18/21, Alexander Epaneshnikov via orca-list <orca-list gnome org> wrote:
On Thu, Nov 18, 2021 at 08:40:02PM +0100, Christian Schoepplein via
orca-list wrote:
Am 18.11.2021 um 20:04 schrieb Nimer Jaber via orca-list
<orca-list gnome org>:
I've used both Bitwarden and 1Password. 1Password is a paid tool, but it
does work.
I’ve used 1Password in the past on Windows, Mac and iOS and is really good
to use on those plattforms. Since the linux version has been released not
so long ago, I’ve not tested it already, but if it is really accessible it
might be a solution if the open source tools do not work.
I will test KeepasX during the next days and if this does not work I’ll
take a look on Bitwarden.
Are the Bitwarden clients for Windows Mac and iOS useable?
hello. I am using Bitwarden on linux, windows and android. there clients
are accessible and I highly recommend Bitwarden is a really good password
manager.
Cheers,
Schoepp
--
Sincerely, Alexander
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]