Tobi Waves

by David Heinemeier Hansen

Rails is a Ruby based Webapp framework that came out of the development of Basecamp. Basecamp is a commercial Web based project management software written by (www.37signals.com ...)

Davids idea when designing rails was to pull out the good ideas from other languages and platforms into a context adapted to small resources available to David at 37signals (0.25 programmers and 1 designer).

Instead of designing the framework before writing Basecamp, David decided to write Rails by creating a method of extracting the framework from Basecamp. So instead of making assumptions about what he would need in the future, he writes Rails in parallel with Basecamp. He calls this application driven development.

How to be successful with an OpenSource project:

Be visible. If no one cares for your OOS project you could as well not "opensource" it, since the cost for publishing will never be recovered.

Release only once the culture of the project is fairly set, so that new influences through new users will not bend the project out of shape. Make sure you can handle the contributions and bug reports from your users.

Increase your visibility by taking on the 'leader-of-the-pack' be careful about aggressiveness though, since if you are aggressive towards others, you will also attract aggressive people to your project.

Nick Gall and IT Analyst

Nick talks about how to design an architecture that is sustainable over the long term? The secret of sustainable architectures is that they are using simple protocols that enable extensibility above as well and below. Simple and successful applications are identified by three properties.

               identifier    format            protocol
               ------------  --------------    ---------------------
examples        ip address    ip packet        ip protocol
email           @ address     rfc 2822         SMTP
web             URL	      HTML/MIME         HTTP
Web Service     URI	      SOAP              SOAP Processing Model
Containerized
Shipping        Container ID  20t Container    Porthandling Protocol 

David Heinemeier Hansson from 37signals

David talks about the "Secrets behind Ruby on Rails". Ruby on Rails is a integrated stack of web-applications frameworks. Basically a framework of frameworks that makes the Webapplication developers lifes fun.

Rails has sparked a huge interest in Ruby for Webapplication development since its publications. There are currently 7 books on Rails in the works and the first one is already published.

The three guiding principles behind Rails design and thus its success are:

Convention over Configuration - As long as you follow the golden path, Rails does things automatically. This results in less code and faster development. You only have to add explicit configuration information when you deviate from the golden path.

Change is instant - This allows a "Use it, break it, fix it, trash it, change it" work pattern. There is no compilation, deployment, server-restarts, and code-generation. This is mainly due to Rubies excellent introspection and open classes that can be extended and modified from user code.

Rails ships as a complete, integrated and familiar stack - this means once you have installed rails, it will start working right away and take care of all the tires of a web application.

Flexibility is highly overrated. Rails trades flexibility for ease of use.

Constraints are liberating! Because you do not have to think about it and take the decisions on your own.

Katik Subbarao from HP

He takes inspiration from the four elements and compares OpenSource to "Water" and closed source to "Earth". Water flows everywhere and is transparent. Earth is solid, opaque and it has to be transported explicitly from one place to another. He draws a 4 quadrant graph:

 Earth
 ^             |
 |  Desert     | Venice 
 |             |
 | -------------------------
 |             |
 |  Swamp      | Ocean
 |             |
 ----------------------------gt Water

You should aim to be in Venice with your IT organization. Buy and build your environment, taking the best from both worlds and become part of the eco system. Contract OpenSource developers to add the Features you need and pay them for support. This will give you contract security and OpenSource transparency at the same time.

Robert Lang on Computational Origami

Today origami designs are created with specialized computer software. Lang showcases spectacular dasigns, all done from a single sheet of paper without cutting. (www.origamidatabase.com ...) and (www.langorigami.com ...)

Dick Hardt from sxip

Dick has a exceptional presentation style. While showing about 10 slides a second he completely captures the audiences attention. See it to believe it.

Dick makes a case for Identity2.0, an electronic equivalent to drivers license, passport, national identity cards to enable Web2.0. Currently you have to register on every website seperately, and most of them rely only on your eMail for identification.

There are several solutions for this in the works, but nothing is widely accepted. Dick predicts that only a solution which leaves control with the individual (I choose whom I show my ID, and the state will never know whom I showed it to) will have a chance.

(www.sxip.com ...)

by Jorand Hubbard and Kevin van Vechten (from Apple)

All OpenDarwin sources are on-line and Google indexed.

One of the most prominent component is (webkit.opendarwin.org ...) the rendering component used in Safari.

If you want to put other OSS software onto your mac go to (darwinports.opendarwin.org ...) which is similar to freebsd ports. Use this to build software from source. If you want to get pre-built packages have a look at (fink.sourceforge.net ...)

OS X ships with many different version of gcc ... use gcc_select to switch the default compiler.

When building Darwin Kernel components, note that while Tiger ships with gcc-4.0 the kernel and its tools are compiled with gcc-3.3. Kernel compilation is governed by a number of environment variables which you have to set explicitly prior to compilation. There are also a number of missing header files.

To resolve all the potential problems you might run into when building Darwin components you may want to use the DarwinBuild Environment from (opendarwin.org ...)

With the darwinbuild command you can easily download and rebuild individual components of the OSX System.

If you are into hacking, OSX you will find all the normal communications from apple rather fluffy. This has mainly todo with the standard audience for this kind of material. Make sure you subscribe to the mailinglists for opendarwin, since all the important and knowledgeable tech people (from apple) are there too and you should be able to get answers at a high technical level. Also if you find a problem, make sure you do file a bug with apples bugreporting system. These bugreports go directly to the responsible technical people within apple.

The main problem with security scanners is that they produce a lot of false positives. If you work with a closed source tool there is no way for you to figure out where the false positives come from. With OSS tools these issues can be resolved easily.

Penetration Methodology

a) Discovery stage with whois, traceroute, google

b) Scanning to figure out which boxes exist

c) Service enumeration (service identification and banner grabbing) do not get confused by services running on the wrong port

d) Exploit known vulnerabilities if you can identify versions of services.

e) Install rootkits and log cleaning tools

Obviously only steps a) to c) are executed by security testing companies.

Google as Security tool

Google does not discriminate private information. Often you can find xsl and doc files in google which had not been put there intentionally.

Another great resource are Webserver directories without index files.

Error messages also get indexed by google. Especially php apps are very helpful in this respect, revealing lots of internal information like path and file names.

Webcams use standard file names, so if you search for these strings you can easily find lots of them.

If you find htpasswd files via google you can pull them, crack the passwords using john and then try password user name combinations on yahoo, google, hotmail. Since users often reuse user names and passwords, these things have a high probability of being successful.

The biggest advantage of google though, is that doing google queries is anonymous and will not be detected by the target.

For greater efficiency one could write a script that uses google webservice apis for automatically doing interesting queries in connection with a certain target.

Nessus

The coolest thing about nessus is that it is very easily extensible. It comes with its own optimized scripting language NASL. The advantage to writing NASL scripts as opposed to writing them in a random scripting language is that NASL scripts plug right into the comprehensive Nessus user interface.

SQL Injections for Web applications

Many web application have only rudimentary input validation.

$sql = " select * from users where user'$a' and password  '$b' "

how about trying to login with

' or true

This would end up as

select * from users where user'ddd' and password '' or true;

The possibilities are limitless. By adding a '; you could even start a completely new command.

Absinthe from (0x90.org ...) is a tool that tries to automate these attacks.

Tools

Metasploit is a point click root tool (metasploit.com ...)

Wikto is an automated google enabled website vulnerability scanner (www.sensepost.com ...)

Ettercap Network MITM attacks, content filtering, sniffing, etc: (ettercap.sourceforge.net < ...)

Whax is live linux distro with lots of AampP tools (iwhax.net < ...)

Asa Dotzler from Mozilla foundation on Linux on the desktop

There are 4 key factors to Linux success on the desktop

migration - the migration path for users must be as simple as possible. This means that there should be a way to copy complete user environments over from windows to linux, including bookmarks, last open files, everything.

stability - there must be a simple unified binary package format across all distros. Backward compatibility between releases must be absolute. API changes must not break existing applications. Mozilla today runs from Windows 98 to Windows 2003 with a single binary distribution.

simplicity - to multiple choices in setup and configuration frighten new users. Installers should not offer choices since new users can not answer these questions. In general the developers should offer a good solution instead of a bag of selectable ones.

comfort - fulfill peoples expectations of how things should work. And what people expect today is largely influenced by windows.

There is increasing incentive for people to move over from windows, because

a) constant expensive windows updates

b) windows is so malware ridden that it approaches the state of un-usability for average users.

So the time to bring more users to Linux on the desktop has never been better than now. The technology is ready.

In the QampA afterward, an Ubuntu person said that the next Ubuntu release will have full HW support for current DELL, HP and IBM laptops.

Edny on OpenSource Genetics

Edny makes a case for the difficulty in getting anything done at all in genetics today because of the devastating effects of patents on all sorts of tiny bits of genetic information. He mentions two websites that are working against this problem by sharing open genetic information: (parts.mit.edu ...) and (www.biobricks.org ...)

Danny O'Brien on CA releasing Ingress as OpenSource

After lenghty details about licensing choices there is an interesting QampA which boils down to: CA has NOT given up Ingress. They are building all their tools on Ingress today, there are more CA people working on Ingress today than before the release.

Tony Gaughan

Talks about creating instructions. He is on of the makers of Howtoons, a excellent series of cartoons on "How To ..." for kids: (howtoons.com ...)

by Yared

ActiveGrid is a IDE for building WebApplications. It is written in python, but it supports not only Python as a language but also PHP and Perl (in progress).

ActiveGrid has support for different databases and graphical representations for database structures, page flows. It uses stadard xml formats (mostly from w3c and oasis) for the representation of all the things you edit graphically. In contrast to other tools ActiveGrid is not a code generator, it works by looking at the structure of tables and processes and works out what todo at runtime. This allows to adapt to the browser that is using the app.

There is built-in support for web services. Web services can be accessed like databases. Or rather databases can be accessed like web services.

The server side runs on in python (currently), php (soon), perl (soon). There is also a special apache module called mod_activegrid. The server side has an elaborate caching architecture to minimize processing at every stage.

(www.activegrid.com ...)

by Aron Boodman

Greasmonkey grew out of bookmarklets where bookmarks contain little bits of javascript instead of webpage urls.

GM is a Firefox extension that lets users alter webpages as they come in. Since you can not really control what the website providers do, this whole website adaption process is a very fluid process. Sort of shell scripting for websites.

Greasemonkey scripts are just normal javascript with a special header section added that gives greasemonkey additional information about where to use the script.

// =UserScript=
// @name	 User Script Template
// @namespace	 (younpup ...)
// @description Test script
// @include     google.com
// @exclude     mail.gmail.com*
alert('Hello World')

Read more on Greasemonkey in (diveintogreasemonkey.org ...)

Get greasemonkey from (greasemonkey.mozdev.org ...)

Web site providers seem to like Greasemonkey since it gives them higher user loyalty. Some websites have eve integrated features that were pioneered by greasemonkey scripts.

Greasemonkey has had several security issues in June, these were fixed with Greasemonkey 0.5. On top of that special changes made to Firefox Deer Park to further improve the security by protecting document and windows globals. Also in FF 1.5, Greasemonkey will be executed in a Sandbox that even better separates it from the influence of malicious documents.

The ultimate book on Javascript "JavaScript: The definitive Guide" (www.amazon.com ...)

Miguel de Icaza about Linux on the Desktop

Novel (5500 people) is moving itself away from Windows. The first stage with a move from MS Office to OpenOffice is already complete. The OS migration has progressed to 50% and should be at 80% by November. This dog food approach gives them a lot of insight into the linux on the desktop problem.

Major tasks are: Making Hardware work and implementing missing functionality in the OS.

All the new Applications Novel does for Linux are implemented in MONO this makes porting from Windows much simpler. MONO currently supports the following CPUs Itanium, Sparc, StringARM, x86-64, s390 and runs on Linux, Solaris, OS X.

Gnome is being migrated to Cairo based vector rendering and to further accelerate things, the X11 display is moved into running on top of OpenGL meaning all rendering is becoming hardware accelerated.

Miguel shows a number of neat demos of the new desktop. Like for example a mplayer windows wrapping around the edge of a 3d box shaped desktop (each side of the box is a desktop) as the mplayer window is moved from one desktop to another. The new desktop stuff will debut in SuSE 10 due in October.

Novell will start something called OpenSuSE in the next few weeks where you can download ISOs of the running system as it is being developed.