FAQ

Revision 27 as of 2009-03-28 16:20:45

Clear message

Official Support

  • What does official security support mean?

    • Members of the Ubuntu Security team are Canonical employees who provide security updates for supported software in the Ubuntu distribution. Security updates are in part prioritized based on severity of impact, exploitability and number of affected users.

  • What software is officially supported by the Ubuntu Security team?

    • Ubuntu is currently divided into four components: main, restricted, universe and multiverse. Packages in main and restricted are supported by the Ubuntu Security team for the life of an Ubuntu release, while packages in universe and multiverse are supported by the Ubuntu community.

  • Who can receive official support?

Repositories

  • How are the "-updates" and "-security" pockets different?

    • -updates includes things that have gone through the StableReleaseUpdates process, and contain various important bug fixes.

    • -security includes only updated packages that contain security-related fixes, and are built to not require anything from "-updates".

  • How are components and pockets used in the builds, and how do they affect security updates?
    • When packages are built, only certain components are available during the build:

      • main: built with only the main component enabled

      • restricted: built with main and restricted components enabled

      • universe: built with main and universe components enabled

      • multiverse: built with main, restricted, universe and multiverse components enabled

    • Ubuntu also has several pockets that further divide the archive: release, security, updates, proposed and backports. The pocket can be found by looking at the Distribution entry of a source package. The release pocket is simply the name of the release, and the other pockets are denoted by <release name>-<pocket>. For example, the release pocket for Ubuntu 8.04 LTS, the Hardy Heron, is simply hardy, while the security pocket for Ubuntu 8.04 LTS is hardy-security. Packages in release, security and updates are supported by the Ubuntu Security team, while packages in backports are supported by the community and packages in proposed are the responsibility of the uploader. When packages are built, only certain pockets are available during the build:

      • release: during the development cycle, this is the only pocket that is used. Once the development version is released, the release pocket is frozen and does not change.

      • security: built with release and security. SecurityUpdateProcedures gives the process used for creating security updates.

      • proposed: built with release, security, and updates

      • updates: packages in updates are not directly built, but rather copied from proposed after they have been tested. See StableReleaseUpdates for details.

      • backports: built with release, security, and updates. See UbuntuBackports for details.

  • How do I automatically install security updates?

Packages

Software

SSH

  • When I run ssh HOST sudo CMD..., I can see the password as I type it. How do I fix that?

    • There is no "tty" allocated when running commands directly via ssh, please add the "-t" flag.

  • When I connect to my ssh server port, I can see a banner with the exact version I'm running. Can we include a patch to disable the version number?

    • There is an upstream bug that gets into detail about this feature, but Ubuntu does not want to carry the patches unless upstream approves.

    • Hiding the version number is Security through obscurity, which is not real security.

    • SSH clients, including OpenSSH, usually parse the version string in order to identify known bugs/features with a particular version of the server. Changing the values could introduce communication problems with certain clients. See compat.c in the OpenSSH source code.

Sudo

  • Why does Ubuntu disable the root account and use sudo instead?

    • See RootSudo for a thorough discussion, but simply put, sudo offers many benefits including (but not limited to):

      • protecting the user from accidentally damaging parts of the system
      • providing a log audit trail
      • preventing brute-force login and ssh attacks to a well known account
      • authentication timeouts
      • fine-grained granting of privileges
  • I am not prompted for my password when I run "sudo" for a second time!

    • sudo is design to keep a "ticket" valid for 15 minutes after you use your password the first time. This is configurable. Please read man sudoers:

             timestamp_timeout
                       Number of minutes that can elapse before sudo will ask
                       for a passwd again.  The default is 15.  Set this to 0
                       to always prompt for a password.  If set to a value
                       less than 0 the user’s timestamp will never expire.
                       This can be used to allow users to create or delete
                       their own timestamps via sudo -v and sudo -k respec‐
                       tively.
  • If sudo authentication does not immediately expire, doesn't that allow for privilege escalation for malware and local users?
    • Giving untrusted users access to your account or running untrusted code can allow privilege escalation via sudo, but Ubuntu does not (and by default cannot) provide protections against users running code as themselves. Some protections against these sort of attacks are:
      • do not open files or run/install programs from untrusted sources
      • enable locking of your screensaver
      • using 'sudo -k' or 'sudo -K' to remove the timestamps (see 'man sudo' for details)
      • adjusting timestamp_timeout in /etc/sudoers (using visudo) (see above, and 'man sudoers' for details)
      • using a virus scanner such as clamav on your files

      • protecting specific applications with Apparmor or SELinux

CategorySecurityTeam