Conferense Program

Friday, February 11 - Session 1

[Thursday Session 1] [Thursday Session 2]
[Friday Session 1]
[Friday Session 2]

Theme: Free UNIX

F11 - 10.10-10.55 FreeBSD Status and Direction

Speaker: Poul-Henning Kamp has been a member of the FreeBSD core team since FreeBSD version 1.1.5. Despite 15+ years with UNIX, he still think we can improve it.

After a brief introduction to FreeBSD Poul-Henning Kamp will tell about where FreeBSD is today where it is heading and why a lot of people prefer FreeBSD to Linux.

F12 - 10.55-11.35 FreeS/WAN: Why Network Security?

Speaker: Richard Guy Briggs got his taste of UNIX-like systems in 1990 while at Corel Systems Corporation, testing interoperation issues with SCO ODT 1.0 on 80386, Solaris on a Sparc IPX and the 16-bit version of Coherent on a 80286 and at the University of Ottawa on DEC Ultrix and IBM AIX systems. The _Jargon File_ was a significant influence. He has been working with Linux since version 0.13 when he saw Internet announcements about it on comp.ox.minix. He subsequently used it to train the artificial neural network temporal integrator for his 4th year undergraduate speech recognition project in September 1992.

Why be concerned with network security? The Internet was created as a government research network where it was assumed that no one was hostile. Since then, it has exploded in use because the public started to gain access to its resources: databases, bandwidth, connectivity. Because of this, Internet security has become much more prominent, comprising of machine and network security. Many are familiar with machine security, limiting access via passwords.

Network security is a more recent urgency, because packet sniffers are now much more accessible to the public. This is why network-layer encryption has become more important. IPSec is a suite of RFCs that define a set of protocols for packet-layer encryption.

Why use Linux? Linux is inexpensive, popular, and runs on a wide variety of hardware and processor families. Proprietary kernels are not always documented correctly. Open-source kernels have the advantage that if something do not exist or do not work as (not) documented, you can read the source to find out how to use it, or send a patch to fix it. What problems did I (we) have and how did we get around them? I will touch on that after giving an overview of IPSEC and FreeS/WAN.

F13 - 11.35-12.15 Linux Network Traffic Control

Speaker: Werner Almesberger, master's in Computer Science from ETH Zuerich in autumn 1992, delevoped ATM switch control software 1993-1994 at the IBM Zurich Research Lab. Since autumn 1994 research assistant at LRC (Laboratoire de Reseaux de Communication), now ICA (Institute for computer Communications and Applications), at EPFL (Ecole Polytechnique Federale de Lausanne). Participated in design and realization of a site information system (ezInfo) while at ETH. Also involved in kernel work (file systems, device drivers, etc.) on Linux since 1992. On-going Linux activities: the LILO boot loader, the psmisc tools, ATM and Differentiated Services on Linux, and recently a bit of hacking in the linux-7110 project, and work on the Canon PowerShot A50 driver of gPhoto.

Recent Linux kernels offer a wide variety of traffic control functions, covering packet classification, policing, and different queuing algorithms. Traffic control elements can be combined in a modular way. The presentation gives an overview of the design and structure of the respective kernel code. Recently, support for Differentiated Services was added to the existing traffic control infrastructure. Also this implementation will be described.