If you have created a custom RightScript in the RightScale interface that uses git to clone a repository and you are running that RightScript on boot following the RightScale git_repo recipe then you likely are having issues. The problem appears to stem from the fact that the environment variables are not completely cleaned up as expected including $GIT_SSH and possibly others. I have a work around noted below along with a line you can enter in your RightScript to clear the $GIT_SSH ENV variable as well.
It can be useful to set temporary environment variables from the command line in Linux. Even more useful is the output of a long command being set to a single environment variable. Below I show an example of setting an environment variable followed by setting an environment variable to the output of a command or string of commands.
If you are working with multiple Nexpose vulnerability scanners it makes sense to want to generate a bunch of Nexpose Scan Templates on one Nexpose Seurity Console and distribute to a bunch of other Nexpose Security Console’s. There is not much documentation I could find on doing this so luckily it is fairly easy. Follow the instructions below to first export a Nexpose Scan Template from a Nexpose Security Console and then import a Nexpose Scan Template to another Nexpose Security Console. The scan templates are stored as XML so exporting consists of copying the XML file from the server running Nexpose to either your local machine or to another server running Nexpose.
Nmap 5.51: Zenmap: Error Saving Snapshot: Surface.write_to_png takes one argument which must be a filename (str)
I upgraded to Nmap 5.51 early this afternoon because a friend asked me to take a look at creating a topology image of a network scan of around 3,000 hosts. After upgrading I opened his scan in Zenmap and attempted to export the topology of the scan as a PNG but I received an error which I at first assumed was an issue on my computer or an issue with the fact that the export to PNG image was taking place on a 64-bit Windows 7 computer however both of those turned out to be incorrect. Below I describe the error in more detail as well as the current newest Nmap version that will allow PNG export, a workaround for the issue, and notes about the response from the Nmap development team that already pushed a fix to SVN only a couple hours after the issue was reported (+1 Nmap devs!).
This afternoon I was using PGAdmin and needed to export some data from a query I had run but realized I wasn’t even sure if PGAdmin had this capability. Typically I would export data using the PSQL command line but since I was already working in PGAdmin I wanted to try and figure out if the capability existed and if so how to do it. After some playing around I was able to figure out how to export PGAdmin data to a CSV (Comma Separated Value) format that would be Microsoft Excel friendly. Follow the directions below to export PGAdmin data to a .CSV file to open in MS Excel.