mailing list archives
Re: Caching seems to interfere with search
From: Juergen Fiedler <juergen.fiedler () gmail com>
Date: Thu, 19 Jul 2012 00:38:30 -0400
Just a quick addendum: I have left msfconsole running for over a day,
and the behavior has not changed.
One would think that the cache should be built by now.
I noticed that if I search for a full CVE ID, it works: 'search
cve:2008-061' returns the expected result,
while 'search cve:2008' does nothing.
Figured that this may be relevant.
On Wed, Jul 18, 2012 at 2:50 AM, HD Moore <hdm () metasploit com> wrote:
You are likely hitting the database prior to the cache being built.
What it should be doing is defaulting to the live in-memory module search
until the cache is marked as final, but there could be bugs.
Ill open a ticket here to look into it.
From: framework-bounces () spool metasploit com
[mailto:framework-bounces () spool metasploit com] On Behalf Of Juergen Fiedler
Sent: Tuesday, July 17, 2012 9:14 PM
To: framework () spool metasploit com
Subject: [framework] Caching seems to interfere with search
I have two up-to-date metasploit v4.4.0, one on plain Debian (sid) ad
one on Ubuntu (11.4).
For the Debian installation, I followed the instructions for
installation from svn slavishly.
With Ubuntu, I played around a little, which resulted in database
integration not working.
Now, when I start msfconsole on Ubuntu, and issue (for example) a
'search cve:2009 type:exploit app:client', I get a warning message:
[-] Warning: database not connected or cache not built, falling back
to slow search
and after a little bit, I get oodles of results.
On Debian, I get the same behavior if I start the search right after
msfconsole comes up.
After a while, when I do the same search, I get nothing. Not one result.
Some other searches, like 'search ssh' still return results, so
searching is not completely broken.
Other data retrieval queries (hosts, services, etc.) seem to work fine.
Has anybody else seen similar behavior, and maybe even found out how
to fix that?
Do I maybe just have to wait until the module cache is rebuilt?
Is there any way to check on the progress on that?