From Newsgroup: alt.comp.software.firefox

On Wed, 3 Sep 2025 08:11:58 -0000 (UTC), Handsome Jack wrote:

I use KeePass, which does the same. Also, you can use a file, instead of a phrase, as the master key.

I have used KeePass for at least 15 years (based on the last-modified
date of my archived installer). While I've been generally happy with
it, particularly the fact that it doesn't require any Internet access
and there's only on file to copy between devices, it has two
shortcomings: (1) the user interface can only be described as
"clunky"; (2) it relies on page titles, so when half a dozen sites
all use "Sign In" as their page title, I have to pick the right key
sequence manually.

A week ago, I finally installed KeePassXC, a fork of KeePass, found
at <https://keepassxc.org/>.

The docs say KeePassXC will import KeePass databases. That's sort of
true, except for the Auto-Type-Window and Auto-Type directives, which
are in the comments section of KeePass entries. KeePassXC uses the
same directives, in a dedicated section of each entry, so you'd think
it would import them into that dedicated section, but you would be
wrong: they are placed in the comments section but otherwise ignored.

Aside from the extra effort involved in re-entering those strings
manually, I've been happy with KeePassXC. (And it's not all bad:
looking at every single entry, I got rid of a bunch of obsolete
entries.) KeePassXC does a better job of distinguishing among those generically named Sign In or Log In windows through its Window
Association box. The interface is a lot more friendly than KeePass's,
and generally I find KeePassXC easier to use. (Like KeePass, the
database is one file, which can easily be copied to other computers;
and there is no Internet interface so everything stays on my
computer.)

I installed KeePassXC without uninstalling KeePass, simply by
assigning KeePassXC a different Auto-Type shortcut key from the one
KeePass uses. FWIW, I was overly cautious: I've never once had to use
KeePass in the week since I installed KeePassXC, so I've removed
KeePass from my Windows startup sequence.
--
"The power of accurate observation is frequently called cynicism by
those who don't have it." --George Bernard Shaw
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.software.firefox

Stan Brown <someone@example.com> wrote at 16:25 this Wednesday (GMT):

On Wed, 3 Sep 2025 08:11:58 -0000 (UTC), Handsome Jack wrote:

I use KeePass, which does the same. Also, you can use a file, instead of a >> phrase, as the master key.

I have used KeePass for at least 15 years (based on the last-modified
date of my archived installer). While I've been generally happy with
it, particularly the fact that it doesn't require any Internet access
and there's only on file to copy between devices, it has two
shortcomings: (1) the user interface can only be described as
"clunky"; (2) it relies on page titles, so when half a dozen sites
all use "Sign In" as their page title, I have to pick the right key
sequence manually.

A week ago, I finally installed KeePassXC, a fork of KeePass, found
at <https://keepassxc.org/>.

The docs say KeePassXC will import KeePass databases. That's sort of
true, except for the Auto-Type-Window and Auto-Type directives, which
are in the comments section of KeePass entries. KeePassXC uses the
same directives, in a dedicated section of each entry, so you'd think
it would import them into that dedicated section, but you would be
wrong: they are placed in the comments section but otherwise ignored.

Aside from the extra effort involved in re-entering those strings
manually, I've been happy with KeePassXC. (And it's not all bad:
looking at every single entry, I got rid of a bunch of obsolete
entries.) KeePassXC does a better job of distinguishing among those generically named Sign In or Log In windows through its Window
Association box. The interface is a lot more friendly than KeePass's,
and generally I find KeePassXC easier to use. (Like KeePass, the
database is one file, which can easily be copied to other computers;
and there is no Internet interface so everything stays on my
computer.)

I installed KeePassXC without uninstalling KeePass, simply by
assigning KeePassXC a different Auto-Type shortcut key from the one
KeePass uses. FWIW, I was overly cautious: I've never once had to use KeePass in the week since I installed KeePassXC, so I've removed
KeePass from my Windows startup sequence.

I quite liked KeePassXC, and most likely would've daily driven it if I
found a easier way to sync it between my laptop and phone. Currently, I
use Bitwarden.
--
user <candycane> is generated from /dev/urandom
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.software.firefox

On Thu, 4 Sep 2025 15:30:06 -0000 (UTC), candycanearter07 wrote:

I quite liked KeePassXC, and most likely would've daily driven it if I
found a easier way to sync it between my laptop and phone.

Easier than what? Connect phone and laptop with a USB cable, and you
should be able to transfer the database file.

Or use Localsend, which transfers files using Wifi. Here's what I
posted about Localsend to comp.mobile.android a few months back:

=================================================================
Apologies if someone has already posted about this; in that case I
must have missed it.

Localsend (free and open source) lets you transfer files between
devices that are on the same Wifi LAN. I've seen and tried many other solutions, but this is the first one that actually worked for me. (I
tried transfers in both directions.)

https://github.com/localsend/localsend/releases/tag/v1.17.0

You load the app on your phone (I found it in the Google Play Store)
and the appropriate version from the above link on your computer.
Yes, you can have more than two devices with Localsend, though I
didn't test that. Each install creates a device identifier name that
is unique to Localsend, to identify the sending device to the
receiver and vice versa.

You need to have Localsend actually running on both devices involved
in the transfer. A nice feature is that in Android when you have a
picture, you can just tap the Share icon and the picture will appear
in Localsend. I transferred a couple of pictures that were a few
hundred K each, and the transfer was instantaneous.

Source:
https://www.howtogeek.com/open-source-android-apps-to-install/

=================================================================
--
"The power of accurate observation is frequently called cynicism by
those who don't have it." --George Bernard Shaw
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.software.firefox

On Thu, 4 Sep 2025 15:30:06 -0000 (UTC), candycanearter07 wrote:

I quite liked KeePassXC, and most likely would've daily driven it if I
found a easier way to sync it between my laptop and phone. Currently, I
use Bitwarden.

To keep the database synchronised you could use the solution I
suggested: save the database file in the cloud, OneDrive for instance,
and keep a key on your phone and one on your laptop/PC. The database
will remain the same for both devices.
--
s|b
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.software.firefox

On 05/09/2025 08:36, s|b wrote:

On Thu, 4 Sep 2025 15:30:06 -0000 (UTC), candycanearter07 wrote:

I quite liked KeePassXC, and most likely would've daily driven it if I
found a easier way to sync it between my laptop and phone. Currently, I
use Bitwarden.

To keep the database synchronised you could use the solution I
suggested: save the database file in the cloud, OneDrive for instance,
and keep a key on your phone and one on your laptop/PC. The database
will remain the same for both devices.

Why would you want/need to keep anything as critical as a KeePass
database on The Cloud? Would you be changing it so often that you
required constant access to any change? Once a hacker has that database
he just needs to wait until the key becomes available, eg with a
keylogger. Why not just make the database change on /one/ machine and
later copy that database to any other machine that needed to use it? <https://www.infosecurity-magazine.com/news/microsoft-onedrive-flaw-exposes/> --
Jeff
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.software.firefox

On Fri, 5 Sep 2025 08:50:37 +0100, Jeff Layman wrote:

Why would you want/need to keep anything as critical as a KeePass
database on The Cloud? Would you be changing it so often that you
required constant access to any change? Once a hacker has that database
he just needs to wait until the key becomes available, eg with a
keylogger.

A hacker would still need the key AND the Master Password. IMO you're
going a long way expecting a hacker would get access to a database in
the cloud AND then connecting it to my PC/smartphone and hack those to
get the key AND then somehow the Master Password (which I manually
enter). I'm not a hacker, but it seems farfetched.

Why not just make the database change on /one/ machine and
later copy that database to any other machine that needed to use it?

That's what I do. I just read about the cloud solution with OneDrive and
the guy considered it pretty save, because a database without a key and password is pretty useless.

<https://www.infosecurity-magazine.com/news/microsoft-onedrive-flaw-exposes/>

One could also use Google Drive or Dropbox or something similar. Doesn't
have to be OneDrive.
--
s|b
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.software.firefox

Jeff Layman <Jeff@invalid.invalid> writes:

On 05/09/2025 08:36, s|b wrote:

On Thu, 4 Sep 2025 15:30:06 -0000 (UTC), candycanearter07 wrote:

I quite liked KeePassXC, and most likely would've daily driven it if I
found a easier way to sync it between my laptop and phone. Currently, I
use Bitwarden.

To keep the database synchronised you could use the solution I
suggested: save the database file in the cloud, OneDrive for instance,
and keep a key on your phone and one on your laptop/PC. The database
will remain the same for both devices.

Why would you want/need to keep anything as critical as a KeePass
database on The Cloud? Would you be changing it so often that you
required constant access to any change? Once a hacker has that
database he just needs to wait until the key becomes available, eg
with a keylogger. Why not just make the database change on /one/
machine and later copy that database to any other machine that needed
to use it? <https://www.infosecurity-magazine.com/news/microsoft-onedrive-flaw-exposes/>

I use KeePassXC, mostly on my desktop, but simply copy the database to
my phones when something changes. After the initial flurry of adding
entries, I find I don't need to add new logons and passwords all that
often. I use Total Commander to copy the database down to the phone over
Wifi using SSH. Easy and quick.
--
-Don_from_AZ-
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.software.firefox

Don_from_AZ <djatechNOSPAM@comcast.net.invalid> wrote:

. . .

I use KeePassXC, mostly on my desktop, but simply copy the database to
my phones when something changes. After the initial flurry of adding
entries, I find I don't need to add new logons and passwords all that
often. I use Total Commander to copy the database down to the phone over
Wifi using SSH. Easy and quick.

I am not familiar with that.

I never copy files to and from the phone using Wifi. I don't want to
introduce another instance of possible compromised security. I copy
files while tethered.
--- Synchronet 3.21a-Linux NewsLink 1.2