remove the old KeePassX completely #636

2018-11-27T08:51:05Z

quiddity-wp commented

2018-11-27 08:51:05 +00:00

(Migrated from github.com)

After 2.5+ years without change, I suggest removing the old KeePassX completely and slightly expanding the explanation for KeePassXC. Thanks!

ghost commented

2018-11-27 09:10:07 +00:00

(Migrated from github.com)

Maybe we could go as far as remove KeePass totally and keep only KeePassXC? I've heard from some people that they use KeePassXC because they don't want to use mono to run KeePassX.

👎 1

beerisgood commented

2018-11-27 11:35:51 +00:00

(Migrated from github.com)

@Shifterovich under Windows the original is still the best

ghost commented

2018-11-27 11:38:04 +00:00

(Migrated from github.com)

In what sense is it better than KeePassXC on Windows? Recommending multiple forks is somewhat confusing. I think we should pick one and recommend only it.

beerisgood commented

2018-11-27 16:19:10 +00:00

(Migrated from github.com)

@Shifterovich There are security differences....

Keepass has Secure Desktop & Two-Channel Auto-Type Obfuscation while KeepassXC doesn't

with Keepass I can create multiple password templates and a default password template for newly generated entries.

Overall I think you have more options and control in Keepass.

@Shifterovich There are security differences.... Keepass has Secure Desktop & Two-Channel Auto-Type Obfuscation while KeepassXC doesn't with Keepass I can create multiple password templates and a default password template for newly generated entries. Overall I think you have more options and control in Keepass.

ghost commented

2018-11-27 16:33:06 +00:00

(Migrated from github.com)

Okay.

This repo is archived. You cannot comment on pull requests.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#636