exploitdb UUID Problem work around.

[Krytical]

I just re-installed backtrack with r2, and haven't been on backtrack in a while...

when I try to update exploitdb using the button in Kmenu>backtrack>penetration>exploitdb>update exploitdb

I first get an error about the wrong UUID or something, so I remembered from doing that before, changing the expected ID to the recieved ID in the .svn entries file

so after that I re attempt the update with this error as the result

"svn: No such revision 6"

but I couldn't figure out how to fix it after that...

[johnnycannuk]

I worked with archangelamael on IRC and this is the method to fix the exploiddb uuid issue:

1. navigate to /pentest/exploits
2. rm -r exploitdb directory
3. mkdir exploitdb
4. from the /pentest/exploits directory issue an svn checkout:

svn co svn://www.exploit-db.com/exploitdb

5. Once you have checkout sucessfully, navigate to the kmenu update and run it.

You should see

At revision 5.
root@bt:/pentest/exploits/exploitdb#


No more uuid errors.

[Archangel-Amael]

EDIT: See above.

The exploitbd package will be rebuilt, for those that just can't wait there is a work around that should resolve the problem of a mismatched UUID when trying to update.

First remove the /exploitdb/ directory from /pentest/exploits/ then make a new one mkdir exploitdb then move into it cd mkdir/ and checkout a new copy of the exploitdb. # svn co svn://www.exploit-db.com/exploitdb This will download a new copy of the database and you should be all set.

As mentioned the package is being rebuilt and will be in the repos soon.

[Impono]

Hello, is this workaround still working?

root@bt:~# cd /pentest/exploits/
root@bt:/pentest/exploits# rm -rf exploitdb/
root@bt:/pentest/exploits# svn co svn://www.exploit-db.com/exploitdb
svn: Network connection closed unexpectedly
root@bt:/pentest/exploits#

[eskim]

Not today!

[Saeth]

Thanks for figuring out this fix. Its working pulling updates perfectly now. Thanks again.