The Fix for Metasploit update in BackTrack 5-R2

Do you get an

[*] msfupdate[*] Attempting to update the Metasploit Framework...[*]
svn: /opt/metasploit/common/lib/libssl.so.0.9.8: no version information available (required by /opt/metasploit/common/lib/libserf-0.so.0)
svn: /opt/metasploit/common/lib/libcrypto.so.0.9.8: no version information available (required by /opt/metasploit/common/lib/libserf-0.so.0)
svn: /opt/metasploit/common/lib/libssl.so.0.9.8: no version information available (required by /opt/metasploit/common/lib/libserf-0.so.0)
svn: /opt/metasploit/common/lib/libcrypto.so.0.9.8: no version information available (required by /opt/metasploit/common/lib/libserf-0.so.0)

error ?

hears the FIX


cd /opt/metasploit/common/lib

mv libcrypto.so.0.9.8 libcrypto.so.0.9.8-b

mv libssl.so.0.9.8 libssl.so.0.9.8-backup

ln -s /usr/lib/libcrypto.so.0.9.8

ln -s /usr/lib/libssl.so.0.9.8

msfupdate

Worked like a charm... Default install after live had the update issue, followed these steps, corrected the issue.


\\Cheers

I did the fix... now I get this

root@root:~# msfupdate[*][*] Attempting to update the Metasploit Framework...[*]

svn: 'external/source/meterpreter/workspace/metsrv' is not a working copy directory
svn: Working copy '.' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
root@root:~# svn cleanup
svn: '.' is not a working copy directory

Any ideas?

Quote:

---

Originally Posted by DiazKnutz

I did the fix... now I get this

root@root:~# msfupdate[*][*] Attempting to update the Metasploit Framework...[*]

svn: 'external/source/meterpreter/workspace/metsrv' is not a working copy directory
svn: Working copy '.' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
root@root:~# svn cleanup
svn: '.' is not a working copy directory

Any ideas?

---

Hi
Try cd /opt/metasploit/msf3/ && svn cleanup && svn up

Thanks zimmaro and jenbo :D

much appreciated

Perfect. Thanks a lot.

worked great many thanks!

Thank you for this. Corrently running 5.2 GNOME. I am going back to KDE though. Sme message still comes with both. Thanks for the fix.

Tack, Kijjite

I've tried this fix and it's still not working.

I now get the following:

svn GET of'/svn/!svn/bc/15243/framework3/trunk/data/armitage-src/src/armitage/ArmitageThreadClient.java': SSL negotiation failed: Connection reset by peer (https://www.metasploit.com)

The svn GET can be replaced by a number of different errors (PROPFIND etc), but it's always failing at some Armitage download and always has "connection reset by peer" message.

I've tried installs of both KDE and GNOME 64-bit both in VM and on a couple of pieces of hardware and both seem to have the issue. My 32-bit GNOME installs all seem to work just fine.

Is there perhaps a problem with the 64-bit installs after some update? It was working fine until yesterday.

Thx

Fix Worked For Me Thanx