adding new exploit modules to v.2.3

[hdm at metasploit.com (H D Moore)]

Cygwin is picky about file permissions, did you use the same username to 
install the Framework, copy the new module, and the re-launch it? If you 
copied the module as a different user (or even just copied from from the 
Windows side), you may need to fix the file permissions before the Cygwin 
side will be able to read the file:

Start a Cygwin shell and try the following commands:
$ cd /home/framework
$ chmod 644 exploits/*.pm

If this doesn't fix the problem, it may be a Windows file system 
permissions issue. Open Explorer and browse to the "home" subdirectory 
under the Metasploit Framework install path. You should be able to just 
right-click the "framework" folder, select Properties, click the Security 
tab, and change ownership of all files in the directory.

The Cygwin permission stuff is the reason why the Framework tar archive is 
not extracted until after the installation finishes (and executed as the 
desktop user, not the installer service). We really need to re-implement 
the whole Win32 installer system...

-HD

On Friday 21 January 2005 09:02, James E. Just wrote:
> We seem to have a problem adding new exploit modules to v. 2.3 under
> Win 2K Pro SP3.
>
> We have an exploit module that we have added to v. 2.2 exploit
> directory and Metasploit immediately identified it and added it to the
> list of exploits with full functionality.  When we do the same thing
> with v. 2.3, Metasploit (at least the msfconsole) does not recognize
> that the new module exists even if we try to call it by name.
>
> When I do the same thing under Windows XP, both versions add the new
> module correctly.
>
> Any thoughts on how to fix this in Win 2K.
>
> Thanks.
>
> Jim Just