Roadmap

Revision 102 as of 2009-10-06 16:21:22

Clear message

Karmic

Blueprints

Documentation

  • The Security Team FAQ needs to be filled with answers to the various questions Ubuntu gets about security.

  • The Security Team KnowledgeBase need more to be written. Many ideas have already been listed there.

Investigations

Several ideas for possible work come from investigating existing the installed set of packages.

  • setuid: which programs are setuid and what may be needed to improve them.

  • measure how many bits of randomness are actually being used in kernel ASLR, compared to other ASLR implementations.
  • review ideas from brainstorm.

AppArmor Confinement

The following profiles have been identified and prioritized as targets for AppArmor confinement. A number of profiles already exist and are not included in this list. Please note that a high priority does not indicate a committment to develop the profile during the current development cycle.

  • Top priority
  • Secondary priority
    • nmbd
    • winbind
    • spamassassin (spamd)
    • acroread (likely not possible due to constraints of agreement with Adobe)
  • Tertiary priority
    • dnsmasq (possibly P2 due to libvirt (talk to soren))
    • squid (possibly P2 (talk to elmo))
    • awstats
    • analog (in progress)

    • mailman
    • asterisk (universe)
    • exim4
    • nagios/nrpe
    • openssh-server (not easy, as users can spawn anything)
    • pidgin
    • mail clients (thunderbird, kmail, evolution) -- difficult
    • eog
    • totem
    • skype (likely not possible due to constraints of agreement)
    • ekiga
    • rhythmbox
  • Unspecified priority
    • portmap (low-effort)
    • rpc.statd (low-effort)
    • scripts that people tend to give sudo access. For example: apache2ctl, initscripts
    • munin

Unscheduled Wishlist Items

This area can be used to list ideas for future security work, or link to bugs that describe "Wishlist" issues.

Not Interested

  • hardened default config (Bastille-like). Check the compatibility of debian-bastille. Status: reviewed. what can be done in a default install is already being done

Community Participation

These are some ideas that came out during the community growth meeting at UDSKarmic:

  • for the SecurityTeam

    • more IRC workshops
    • blog more
    • always participate in Ubuntu Developer Week
    • participate with Hall of Fame or 5-a-day
    • work even more closely with Debian
  • Encourage community involvement:
    • perhaps a "Universe packages of the week?" (only if you are also available (we'll be in #ubuntu-security on ...))
    • some focused event like suspend/resume with kernel team or maybe hug days. This could be done with apparmor profiles ('Apparmor Week')
    • participate with security documentation
    • testing
      • automated test cases could be created for each release (autohotkey for Windows allows to replay GUI actions for testing a PoC)
      • perhaps look into applications to replay actions
    • have a ppa to pull profiles from profile repositories and make them available
    • make testing very easy
      • make-test-tarball is a start, but also need to create VMs easily. vm-tools is a start, but needs to be even easier (maybe grab an image from somewhere...)
    • talk to server team about a survey about features. many of these will likely be security features
  • Disseminating information
    • communicating the security team's needs can be handled (in part) by the community team
    • communication about needed apparmor profiles could be improved
    • maybe talk about what our needs are (eg universe, apparmor profiles, etc)
    • have harvest better integrate with security fixes (talk to dholbach and jorge)

    • focus and ask what is keeping people from adopting Ubuntu
      • we should also identify several areas where we become experts and give all the information-- eg if a salesperson is in front of a potential client and is asked 'tell me about all your logging software' or 'tell me all the ways you handle user credentials and authentication'
  • look into USN-C (community USN) and a way to attach the name of the committer/uploader as a way to increase involvement (though better reputation)


CategorySecurityTeam