More option for URL/domain matching when IP address is used

[rtomaszewski]

hello,

My system: windows 7, latest chrome, keepass and keepasshttp.

Problem: I need to login on regular basis to many systems whose URL looks like this:

(*) https:///path/login.jsp

where the IP address is a regular IP that changes from system to system. There are no domain name for these systems so the IP is the only option to connect to them.

I have my own user and password that can be use on all of the systems and it is rotated on a regular basis.

I've tried to create various URLs or Titles (when configuring a new entry in Keeppass) to login automatically but I was unable to come with anything working for more than a single site.

I've seen some of ideas people suggested how to resolved this but none of them worked for me:

-https://github.com/pfn/keepasshttp/issues/97 -https://github.com/pfn/keepasshttp/issues/130 -https://github.com/pfn/keepasshttp/issues/18 (this is for firefox although a similar problem like mine) -https://github.com/mpern/keepasshttp/blob/master/README.md#url-matching-how-does-it-work, the section about Levenshtein Distance

In best scenario I would like to have

• regular expression support for domain (*) when defining Title or URL in keypass entries.
• other idea how/what to match in keypass database when the domian (*) is typed in browser?

Thanks and regards Rado

[mpern]

The problem is the changing IP-Address. As far as I remember keepasshttp first searches with the domain/IP in keepass and performs the matching on the results of the search afterwards.

For your szenario to work you would have to iterate over every entry and check if the pattern in title or URL matches the Query-URL

How does the rotation in your szenario work? Is it a fixed set of IPs? If so, you could define one master entry and create duplicates that reference to the master entry for every IP in the set as workaround (see this section in the readme)

[rtomaszewski]

I was thinking about this option as well. But I work for a service provider and we manage thousand of devices. That means we speak about many, uncorrelated IPs. The only common thing is that all the IPs are from a private network like 10.0.0.0/16.

Any other ideas?

[mpern]

I think this use case isn't considered in the current implementation... But what do I know, I just poked around a bit. ;)

@pfn Maybe the original author has an idea?

[jaimeagudo]

I suggest to use dynamic dns for these machines if possible or, a local trick, dynamically change your hosts file with any script

[alexz0nder]

Juuuuust perfect !!! It's already 2017 and I still can't find the way to use one user/password for a bunch of IP-addresses? Is the issue already solved?