All steps are to be run as root.
Step #1: install RubyGems:
apt-get install rubygems
Step #2: update RubyGems:
gem install rubygems-update --version=1.3.4
Step #3: get Rails 2.3.5:
gem install rails --no-rdoc --no-ri
Popularity: 3% [?]
A few weeks ago we published the Open Source Vulnerability Database (OSVDB) Import Plugin for the Dradis Framework. At that point we thought that it would be nice to separate the code and create an independent Ruby module that can be used to query the OSVDB.
It turned out that an osvdb project already existed in RubyForge so we have submitted our code there.
There are no releases so far but the code in the repository is working. In order to get it:
svn checkout http://osvdb.rubyforge.org/svn/trunk osvdb
As well as implementations for the ‘Find by Microsoft Security Bulletin ID’ and ‘OSVDB ID Lookup’ queries, the repository contains test cases and a Rakefile to generate RDoc documentation for the library.
Stay tuned for updates.
Popularity: 1% [?]
Although we presented some of this concepts already in dradis reporting: quick & neat word export, here is the step by step guide to get an export plugin recognised by the dradis framework and ready to use!
Update (2009-04-09): Checkout the new import/export plugin generators at dradis community forums.
Continue reading “How to create a dradis export plugin?”
Popularity: 11% [?]
We have already seen how to Use Rails to Create a Static Site. In that article we left the site running, and we recommended the use of wget to generate the static copy. Although this is good enough, with a little bit of Rake we can make deployment easier.
Continue reading “Use Rails to Create a Static Site: Rake and Subversion”
Popularity: 9% [?]
Dradis is a tool used for structured information storage and sharing. Although it is applicable to various environments, it is originally aimed at information security consultants working alone or in a team. One of the great features of the application is that the client side’s functionality can be extended by what is called (quite creatively) – extensions.
In this post I’ll be looking at what an extension is, how it fits into the dradis framework and how to write your own extensions.
You are welcome to jump ahead to the How do I write my own extension? if that is the only part that you are interested in.
Continue reading “dradis extensions: how they work and how to write them”
Popularity: 11% [?]
With over 800 downloads in the first two weeks of dradis v2.0, there is lots of interest on what is going to be next. We are working on solutions for importing and exporting data to and from the repository, but for those of you that can’t wait, we have put together a plug-in for the server that exports your notes to a Word file.
It is not the final solution, and it is not integrated with the web interface, but hopefully it will give you an idea of how easy is to get your own exporting modules for dradis.
Continue reading “dradis reporting: quick & neat word export”
Popularity: 13% [?]
In this part of the series (see Part 1 and Part 2) we will:
- Make one of the components compulsory to install.
- We will look at a way to write our script in such a way that it can be reused for future releases of MyApplication.
- A few extra tips and tricks.
Continue reading “NSIS installer for a Ruby application – Part 3 – A few script improvements”
Popularity: 11% [?]
In Part 1 of this series we had a look at the general structure of a NSIS script as it was created for us by the HM NIS editor and IDE. We previously defined three components to be installed by our installer:
- Ruby (the target machine that our application is installed on requires Ruby)
- MyGem (our application is dependent on this fictitious gem)
- MyApplication (this is our application to be installed)
In this part we will look at how we will let the installer take care of the Ruby and MyGem components.
Continue reading “NSIS installer for a Ruby application – Part 2 – Install Ruby and a gem”
Popularity: 12% [?]
One of the new things we released last week with dradis v2.0 was a new web site for the project (dradis.sourceforge.net).
The old site consisted of 20 static pages or so, which was nice and easy but a real pain to maintain or restructure. So we thought that letting Rails do the heavy lifting for us would be a good idea, but we did not want to set up a Rail environment in the server…
What we finally did is use Rails as a tool to create a static site that we could .tar.gz and upload to the server. As a starting point we used a post in www.chuckvose.com and this is how we completed it to fit our needs.
Follow up (2009-03-23): do not miss how to integrate your rails-static site with Rake and Subversion in the second article of this series: Use Rails to Create a Static Site: Rake and Subversion.
Continue reading “Use Rails to Create a Static Site”
Popularity: 100% [?]
Tags: Add new tag
I am working on an NSIS (Nullsoft Scriptable Install System) installer for a Ruby application (Dradis – check it out!). In this series I will try to keep log of how I progress with this.
I am using HM NIS editor and IDE for NSIS to make the task a little easier. To get out of the blocks a little quicker I used the HM NIS wizard to create a simple framework from where I will progress.
Continue reading “NSIS installer for a Ruby application – Part 1 – HM NIS wizard output”
Popularity: 15% [?]