Nmap Development mailing list archives
Re: [RFC] Zenmap search interface overhaul
From: Fyodor <fyodor () insecure org>
Date: Tue, 27 May 2008 17:43:44 -0700
On Tue, May 27, 2008 at 01:30:34PM -0600, David Fifield wrote:
On Tue, May 27, 2008 at 09:15:22PM +0200, Vladimir Mitrovic wrote: Neither. It means "all scans after 00:00 on January 9." Fuzziness should only increase, never decrease, the range of dates searched. Similarly before:~date would push the date forward in time a day. Again we have to make a decision. Does before:2008-01-10 mean, "before 00:00 on January 10" or "before 00:00 on January 11"? In other words, does "before" really mean "on or before"? My inclination is to choose the more expansize option, "on or before", just like "after" is "on or after". So for this example "before:~2008-01-10" means "all scans before 00:00 on January 12."
Hi David. I think you have some great ideas related to search keywords. But I'm not sure I understand the value of ~ "fuzzyness". It sounds like after:2008-01-10 already includes anything on that day or later in your plan. If I want to add a day to be on the safe side or because I'm not sure of semantics, wouldn't specifying after:2008-01-9 be just as easy and more intutive than after:~2008-01-10? And if I want 3 extra buffer days, why would after:~~2008-01-10 be any simpler than after:2008-01-07? Who is going to remember a special syntax for adding an extra day or three, when they can just add or subtract the days from the date given directly?
Why have the fuzziness, when it's just a shorthand for operations with precise semantics? The answer is that I don't want to have to remember precise semantics when I'm searching.
If someone doesn't remember whehter after: and before: include the day in question, what are the odds that they will remember the meaning of "~" and "~~"? Cheers, -F _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Re: [RFC] Zenmap search interface overhaul, (continued)
- Re: [RFC] Zenmap search interface overhaul jah (May 23)
- Re: [RFC] Zenmap search interface overhaul Vladimir Mitrovic (May 23)
- Re: [RFC] Zenmap search interface overhaul David Fifield (May 23)
- Re: [RFC] Zenmap search interface overhaul eldraco (May 23)
- Re: [RFC] Zenmap search interface overhaul Vladimir Mitrovic (May 24)
- Re: [RFC] Zenmap search interface overhaul Vladimir Mitrovic (May 26)
- Re: [RFC] Zenmap search interface overhaul David Fifield (May 27)
- Re: [RFC] Zenmap search interface overhaul Vladimir Mitrovic (May 27)
- Re: [RFC] Zenmap search interface overhaul Vladimir Mitrovic (May 27)
- Re: [RFC] Zenmap search interface overhaul David Fifield (May 27)
- Re: [RFC] Zenmap search interface overhaul Fyodor (May 27)
- Re: [RFC] Zenmap search interface overhaul David Fifield (May 27)
- Re: [RFC] Zenmap search interface overhaul Fyodor (May 28)
- Re: [RFC] Zenmap search interface overhaul eldraco (May 23)
- Re: [RFC] Zenmap search interface overhaul jah (May 23)
- Re: [RFC] Zenmap search interface overhaul David Fifield (May 27)
- Re: [RFC] Zenmap search interface overhaul Vladimir Mitrovic (May 27)
- Re: [RFC] Zenmap search interface overhaul Fyodor (May 27)
- Re: [RFC] Zenmap search interface overhaul Vladimir Mitrovic (May 28)
- Re: [RFC] Zenmap search interface overhaul David Fifield (May 30)
- Re: [RFC] Zenmap search interface overhaul Vladimir Mitrovic (May 31)