All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] security subsystem: Smack updates for v4.19
Date: Thu, 16 Aug 2018 08:34:50 +1000 (AEST)	[thread overview]
Message-ID: <alpine.LRH.2.21.1808160831490.19586@namei.org> (raw)

Please pull these Smack updates for v4.19, all of which are minor fixes 
from Piotr Sawicki.


The following changes since commit 87ea58433208d17295e200d56be5e2a4fe4ce7d6:

  security: check for kstrdup() failure in lsm_append() (2018-07-17 21:27:06 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-smack

for you to fetch changes up to df6b4e6608eebc2ff18113706f4e3b9d9a972e68:

  Merge branch 'smack-for-4.19-a' of https://github.com/cschaufler/next-smack into next-smack (2018-07-30 10:31:54 -0700)

----------------------------------------------------------------
James Morris (1):
      Merge branch 'smack-for-4.19-a' of https://github.com/cschaufler/next-smack into next-smack

Piotr Sawicki (3):
      Smack: Fix handling of IPv4 traffic received by PF_INET6 sockets
      Smack: Check UDP-Lite and DCCP protocols during IPv6 handling
      Smack: Inform peer that IPv6 traffic has been blocked

 security/smack/smack_lsm.c | 22 ++++++++++++++++------
 1 file changed, 16 insertions(+), 6 deletions(-)

-- 
James Morris
<jmorris@namei.org>


WARNING: multiple messages have this Message-ID (diff)
From: jmorris@namei.org (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [GIT PULL] security subsystem: Smack updates for v4.19
Date: Thu, 16 Aug 2018 08:34:50 +1000 (AEST)	[thread overview]
Message-ID: <alpine.LRH.2.21.1808160831490.19586@namei.org> (raw)

Please pull these Smack updates for v4.19, all of which are minor fixes 
from Piotr Sawicki.


The following changes since commit 87ea58433208d17295e200d56be5e2a4fe4ce7d6:

  security: check for kstrdup() failure in lsm_append() (2018-07-17 21:27:06 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-smack

for you to fetch changes up to df6b4e6608eebc2ff18113706f4e3b9d9a972e68:

  Merge branch 'smack-for-4.19-a' of https://github.com/cschaufler/next-smack into next-smack (2018-07-30 10:31:54 -0700)

----------------------------------------------------------------
James Morris (1):
      Merge branch 'smack-for-4.19-a' of https://github.com/cschaufler/next-smack into next-smack

Piotr Sawicki (3):
      Smack: Fix handling of IPv4 traffic received by PF_INET6 sockets
      Smack: Check UDP-Lite and DCCP protocols during IPv6 handling
      Smack: Inform peer that IPv6 traffic has been blocked

 security/smack/smack_lsm.c | 22 ++++++++++++++++------
 1 file changed, 16 insertions(+), 6 deletions(-)

-- 
James Morris
<jmorris@namei.org>

             reply	other threads:[~2018-08-15 22:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15 22:34 James Morris [this message]
2018-08-15 22:34 ` [GIT PULL] security subsystem: Smack updates for v4.19 James Morris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.2.21.1808160831490.19586@namei.org \
    --to=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.