Multiple URLs

[ckotte]

This issue is a

• bug
• feature
• question

Please describe how you think it should change.

I have some entries that require multiple URLs. For example, same (Active Directory) user account for multiple web sites. Is it possible to read an additional URL from a custom field?

I know that I can also clone the entry and use references for username and password, but I would like to avoid that.

[subdavis]

I'd accept a pull request, but this isn't something I'll probably work on myself.

This is more of a KeePass core function than a Tusk one - ChromeIPass for example wouldn't give you this feature unless it were implemented in KeePassXC.

What I will consider is taking into account information in the "Notes" field when making suggestions. So if you wanted to put "corporate.email.domain" in your notes, in lieu of an exact match, it could take this into consideration.

Thanks for the suggestion. I'll think about how/if this should be supported.

[ckotte]

Looks like there's no such feature in KeePass core / KDBX / KeePassXC yet [1][5]. The only official procedure is to clone the entry and use references [2][3].

The add-on Kee uses a custom JSON object [1]. KeePassHttp/ChromeIPass can at least read custom attributes that start with KPH: [4], but I couldn't find any information if this works with additional URLs.

I think the only way to enable such a feature with Tusk without using references would be to create a custom solution with custom attributes like TUSK_URL1, TUSK_URL2, etc. and search all entries for matching URLs in those fields.

[1] keepassxreboot/keepassxc#398
[2] keepassxreboot/keepassxc#274
[3] keepassxreboot/keepassxc#75
[4] https://github.com/pfn/keepasshttp
[5] pfn/keepasshttp#340

[subdavis]

Your research is uncommon and appreciated. The implementation you're suggesting is completely reasonable

I'm in the middle of adding Yubikey HMAC-SHA1 Challenge Response to support the feature from KeePassXC. Once that work is done, I'll take a look at this.

[ckotte]

Welcome.

Looks like it's a bit difficult to introduce enhancements like this to other implementations of KeePass if it's not included in the Windows version that looks like to be the "KeePass standard".

The good thing, however, is that the username and password referencing works with all implementations I'm using (KeePassXC, Tusk, Keepass2Android, and MacPass)...

[KeePassXC] keepassxreboot/keepassxc#863
[Keepass2Android] PhilippC/keepass2android#227

[subdavis]

@ckotte #87 submitted. I'll let you take a quick look to be sure that will satisfy your use case.

Thanks for the suggestion.

[ckotte]

@subdavis

Sorry for the late response.

Looks good. However, I didn't check your code ;-)

I assume it uses the same matching logic,right? A tab with "#85" would match TUSK_URLS "https://github.com/login?return_to=%2Ffniephaus%2Falfred-homebrew, www.amazon.com,www.google.com"?

[subdavis]

On the web store now. Going to close this out.

[zmilonas]

Now that we have working reference resolving in the extension is it possible to remove this TUSK_URLs - maybe with a warning to all users still using it in a future version.
My reasoning is that we should strive to make the client as cross-compatible as possible and not add extension specific fields if not necessary. Multiple entries with references seems to be more the Original KeePass way.