I didn't realized it until I tried to update the database directly and found out that the Name field "RangeName" in the table "hm_securityranges" must be unique.
Here's a hypothetical scenario:
Am I just fantasizing? Or this could possibly happen?A hacker tries to guess password for one particular account (let's say firstname.lastname@example.org) from IP Address #1 from one network. After few attempts this IP address would get blocked and labeled as "Auto-ban: email@example.com", so the hacker can potentially use another IP#2 to continue attempts. He would get... what... 3-5 more attempts until IP#2 would get blocked.
And here's the problem: The IP#1 record would get overwritten with the new IP#2 address, because of the same unique label, before IP#1 suppose to be expired. Now the hacker can immediately continue his "quest" using IP#1, since it is no longer blocked. After the limited number of attempts he can switch back to #2, and keep repeating that forever.
And if it could, then seems like this scenario could be easily avoided if IP Range Names field would be allowed to have the same names.
Which leads to the main question: what's the reason for enforcing the uniqueness?