Smart Folder - Qualifying Password Strength

seeemef

<div class="IPBDescription">Bounds checking seems erroneous</div>In an earlier post, Khad enumerated the named password strength ranges:



1-10 Terrible

11-20 Weak

21-40 Fair

41-60 Good

61-90 Excellent

91-100 Fantastic



Smart folders allow only two comparisons: "less than or equal to" or "greater than or equal to."



To test the operators, I created three smart folders:



"'Fair' or worse"

Password strength: less than or equal to Fair

Kind: Login

Count = 3



"'Good' or worse"

Password strength: less than or equal to Good

Kind: Login

Count = 14



"Good"

Password strength: less than or equal to Good

Password strength: greater than or equal to Good

Kind: Login

Count = 2



Given these definitions, I expect the "Good" folder to contain the difference between "'Good' or worse" and "'Fair' or worse"; or 11 items, but only 2 were included. Would you please advise whether I am misunderstanding something in these definitions?



Also, it would be helpful to have two additional operators, "less than" and "greater than," in order to allow creating mutually-exclusive smart folders.



Thank you.

chadseld

I'm not sure if you had a typo in the last "Good" folder description. As stated, that search will only return items that are equal to Good since both the predicates must be matched. I assume you are using the "All of the following are true" setting. If you use "Any of the following are true" then that search would return every item.



What you want is:

"All of the following are true"

Password strength: less than or equal to Good

Password strength: greater than or equal to Fair



As for additional "less than" and "greater than" operators, they are not terribly useful due to the mechanics of how password strength matching works under the hood. A passwords strength is calculated as a number between 0 and 100. For simplicity during search, we have broken this range into categories. Khad was mostly right, except these categories do not represent ranges, they represent fixed values.



Terrible = 10

Weak = 20

Fair = 40

Good = 60

Excellent = 90

Fantastic = 100



The actual passwords strengths rarely exactly match these arbitrary boundaries. The exception is "Fantastic" where super strong passwords are capped at a value of 100.



So,

Password strength: less than or equal to Good --> less than or equal to 60

Password strength: greater than or equal to Fair --> greater than or equal to 40



I hope that helps.

DBrown

[quote name='chadseld' timestamp='1300898021' post='23037']

I'm not sure if you had a typo in the last "Good" folder description. As stated, that search will only return items that are equal to Good since both the predicates must be matched. I assume you are using the "All of the following are true" setting. If you use "Any of the following are true" then that search would return every item.[/quote]

I take the "All of the following are true" as a given in all of his definitions.



[quote]

What you want is:

"All of the following are true"

Password strength: less than or equal to Good

Password strength: greater than or equal to Fair

[/quote]

If I understand it correctly, "less than or equal to Good" would list items with strength 0–60, and "greater than or equal to Fair" would list items with strength 40–100; so this smart folder would list items with strength 40–60.



That would be a "Fair and Good" list, not the desired "Good" list.

seeemef

Earlier versions allowed qualification of numeric password strengths, so Khad's ranges make more sense than naming boundaries.



With named boundaries, your definition of a "Good" filter (below) includes the clause "equal to Fair," which is not at all intuitive, and I think indefensible.



It would make more sense (again, in line with Khad's clearer definition) to have "less than or equal to Good" be <= 60 and "greater than or equal to Good" be > 40 .



[quote name='chadseld' timestamp='1300898021' post='23037']

What you want is:

"All of the following are true"

Password strength: less than or equal to Good

Password strength: greater than or equal to Fair

[/quote]

chadseld

[quote name='seeemef' timestamp='1300899971' post='23041']

Earlier versions allowed qualification of numeric password strengths, so Khad's ranges make more sense than naming boundaries.



With named boundaries, your definition of a "Good" filter (below) includes the clause "equal to Fair," which is not at all intuitive, and I think indefensible.



It would make more sense (again, in line with Khad's clearer definition) to have "less than or equal to Good" be <= 60 and "greater than or equal to Good" be > 40 .

[/quote]



I will change the labels to indicate values instead of ranges. Thank you for pointing this out <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />