Technology Insights

SVN: This client is too old to work with working copy

I recently came across a error with subversion which seems to happen on Ubuntu / Debian based distros which utilize the apt-get package management system. Its a small bug and a easy fix however it did take me a little time to figure it out so I felt like maybe a short post might help the next guy.

The Exact Error:

svn: This client is too old to work with working copy ‘/pentest/exploits/framework3’.  You need
to get a newer Subversion client, or to downgrade this working copy.
for details

I got this particular error while trying to svn update the metasploit framework on Backtrack 4, however, I also got the same error while trying to update redmine the other day via svn. The solution is quite simple, what happens is the the .svn hidden files in a svn co directory fail to update for some reason so  when when you issue the svn up command, the project thinks your svn version is out dated.

Technology Insights

Daemon In Linux To Open A TCP Port That Listens On Every IP And Logs TCP Connections

Yesterday a colleague at my company was doing some testing with a potential partner and they needed to open a TCP port on one of our development servers so an application could bind to that port. At first I wasn’t sure how I should do this since the port didn’t need to do anything but listen for incoming connections and the remote application would simply connect to that port. To get something up immediately for them I simply had our web server listen on the requested port which worked however I did not want the web server running on this port for long so I needed to come up with another solution to simply open the port, listen for connections, and possibly log those connections so we could troubleshoot if necessary. I ended up finding an application called tcpsnoop which I explain how to compile and use below.

Technology Errors

Cron Bash Script Error: /usr/bin/env: ruby: No such file or directory

I needed to create a bash shell script tonight that called another shell script with options that then would load a Ruby environment and execute certain commands within a Ruby project. I ran into numerous issues but most were silly things such as typos or other minor issues caused by myself. The one issue I had a little trouble figuring out because of the file that was causing the error related to cron not being able to run “/usr/bin/env: ruby”. My bash script worked perfectly from the Linux CLI shell however when attempting to run it I would always get the same error. Below I list details about the error, where I finally located what the error was, and how to resolve the error.