• SecureBrowser

This is a project to develop a hardened browser, that fulfills the security requirements for general secure Internet usage.

• No Extensions possible (No BHO´s, No Active-X, No Java, No Plugins, No Extensions)
• Statically compiled
• Stripped

• Binary Security: http://www.blackhat.com/presentations/bh-europe-06/bh-eu-06-biondi/bh-eu-06-biondi-up.pdf

• No outside access (DOM externally available)
• Strongly included SSL engine (no modularity between browser core and SSL engine)
• Branding must not conflict with licensing
• Freely available
• Good security enhancing tools included
• Built in Pet names and other useful end user security
• Default URL bar, turn red if there was a non-https URL

Would be nice:

• Good Usability for certificates
  • Fine-grained control of which certificates are presented to which sites
• PKCS#11 API available for crypto hardware
  • PKCS#11 drivers need to be compiled into the main executable, and stripped. no dlopen() or equivalent should be allowed.
• Multiple variations of http/https
  • Status Quo
  • HTTP URLs turn the URL bar red
  • Disable HTTP
• Self booting ISO for secured ISO?

PKCS#11 Considerations: Both OpenCT and pcsc-lite provide interconnect via UNIX Domain Sockets for card reader access. OpenCT can also provide TCP/IP or Unix Domain Sockets ifdproxy for accessing the card reader. Since the card reader driver varies from vendor to vendor and the access is done via sockets, application memory space is immune to corruption, if proper checks are done Device-dependent drivers would be scary to code if we want portability, and hotplugging would be a nightmare. A requirement for a responsible daemon sounds sane enough. OpenSC project's OpenCT is growing fast and seems promising. Works on Windows and many nixes, flawlessly. pcsc-lite is the legacy daemon, with most drivers available, and is an attempt to implement something like the Windows PC/SC infrastructure. Both OpenCT and pcsc-lite can use the drivers from each other if both daemons are running, via bridge drivers.

Project Team

• Philipp Gühring
• Evaldo Gardenali

Please add yourself to the list if you are interested.

Project Plan

• Build up the core-team
• Setup the code repository
• Create the first demo, minimum requirements, only one Platform.
• Create and implement most of the patches
• Build useable builds for all platforms

Project Repository

The project repository is a Subversion repository. You can checkout your copy with svn co http://www2.futureware.at/svn/sourcerer/SecureBrowser To get write permission, please contact Philipp.

Assigned Tasks

The marked entries are necessary tasks for the first Demonstration version.