12 May, 2010

1 commit


25 Mar, 2010

4 commits


18 Mar, 2010

1 commit


08 Oct, 2008

6 commits


10 Jun, 2008

1 commit

  • The following patch implements a new "security" table for iptables, so
    that MAC (SELinux etc.) networking rules can be managed separately to
    standard DAC rules.

    This is to help with distro integration of the new secmark-based
    network controls, per various previous discussions.

    The need for a separate table arises from the fact that existing tools
    and usage of iptables will likely clash with centralized MAC policy
    management.

    The SECMARK and CONNSECMARK targets will still be valid in the mangle
    table to prevent breakage of existing users.

    Signed-off-by: James Morris
    Signed-off-by: Patrick McHardy
    Signed-off-by: David S. Miller

    James Morris
     

14 Apr, 2008

1 commit


29 Jan, 2008

4 commits


30 Nov, 2007

1 commit

  • Fix forgotten module release in xt_CONNMARK and xt_CONNSECMARK

    When xt_CONNMARK is used outside the mangle table and the user specified
    "--restore-mark", the connmark_tg_check() function will (correctly)
    error out, but (incorrectly) forgets to release the L3 conntrack module.
    Same for xt_CONNSECMARK.

    Fix is to move the call to acquire the L3 module after the basic
    constraint checks.

    Signed-off-by: Jan Engelhardt
    Signed-off-by: Patrick McHardy
    Signed-off-by: Herbert Xu

    Jan Engelhardt
     

16 Oct, 2007

1 commit


11 Jul, 2007

3 commits


26 Apr, 2007

1 commit


09 Feb, 2007

1 commit


14 Dec, 2006

1 commit


23 Sep, 2006

4 commits


18 Jun, 2006

1 commit

  • Add a new xtables target, CONNSECMARK, which is used to specify rules
    for copying security marks from packets to connections, and for
    copyying security marks back from connections to packets. This is
    similar to the CONNMARK target, but is more limited in scope in that
    it only allows copying of security marks to and from packets, as this
    is all it needs to do.

    A typical scenario would be to apply a security mark to a 'new' packet
    with SECMARK, then copy that to its conntrack via CONNMARK, and then
    restore the security mark from the connection to established and
    related packets on that connection.

    Signed-off-by: James Morris
    Signed-off-by: Andrew Morton
    Signed-off-by: David S. Miller

    James Morris