Skip to content
Snippets Groups Projects
Select Git revision
  • doc/17717-update-torproject-links
  • update-torproject-links
  • doc/16987-doc-usb-tethering
  • doc/8666-how-to-screenshots
  • doc/8948-persistent-storage
  • web/17549-no-dead-end-on-download
  • doc/17183-import-gpg-key
  • doc/17492-secure-boot
  • doc/15783-vpn-faq
  • doc/17444-screenshot-wrong-OS
  • new-home-about-pages
  • doc/17116-improve-known-issue-persistence-conf
  • doc/17298-migrate-keyserver
  • feature/17219-replace-torbirdy
  • doc/8948-persistence-terminology
  • feature/17197-clarify-rsync-command
  • doc/16975-confusing-doc-del-imgs
  • doc/17190-remove-ref-irc-acct
  • master default protected
  • doc/10885-better-upgrade-doc
  • 3.7
  • 3.6.2
  • 3.6.1
  • 3.6
  • 3.6-rc1
  • 3.5
  • 3.4
  • 3.3
  • 3.2
  • 3.2-rc1
  • 3.2-alpha2
  • 3.2-alpha1
  • 3.1
  • 3.0.1
  • 3.0
  • 3.0-rc2
  • 3.0-fake1
  • 3.0-rc1
  • 3.0-beta4
  • 2.12
40 results

hardening.feature

Blame
    • Forked from tails / tails
    2232 commits behind, 6 commits ahead of the upstream repository.
    hardening.feature 498 B 
    @product
Feature: Hardening features

  Scenario: AppArmor is enabled and has enforced profiles
    Given I have started Tails from DVD without network and logged in
    Then AppArmor is enabled
    And some AppArmor profiles are enforced

  Scenario: The tor process should be confined with Seccomp
    Given I have started Tails from DVD without network and logged in
    And the network is plugged
    And Tor is ready
    Then the running process "tor" is confined with Seccomp in filter mode