From: Fan Wu <wufan@kernel.org>
To: linux-security-module@vger.kernel.org
Subject: [PATCH 6/6] ipe: update the project and test suite links
Date: Fri, 2 Oct 2026 19:51:35 -0700 [thread overview]
Message-ID: <20261003025135.3666767-7-wufan@kernel.org> (raw)
In-Reply-To: <20261003025135.3666767-1-wufan@kernel.org>
IPE now has a project website at https://ipe-lsm.org/, and its
integration tests are maintained in the Integrity-Policy-Enforcement/ci
repository.
Point the admin guide to the website, and point the test suite link in
the developer documentation to the new repository.
Assisted-by: LLM
Signed-off-by: Fan Wu <wufan@kernel.org>
---
Documentation/admin-guide/LSM/ipe.rst | 2 +-
Documentation/security/ipe.rst | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/admin-guide/LSM/ipe.rst b/Documentation/admin-guide/LSM/ipe.rst
index a756d8158531..978773a256e4 100644
--- a/Documentation/admin-guide/LSM/ipe.rst
+++ b/Documentation/admin-guide/LSM/ipe.rst
@@ -791,7 +791,7 @@ Allow execution of a specific fs-verity file
Additional Information
----------------------
-- `Github Repository <https://github.com/microsoft/ipe>`_
+- `IPE website <https://ipe-lsm.org/>`_
- :doc:`Developer and design docs for IPE </security/ipe>`
FAQ
diff --git a/Documentation/security/ipe.rst b/Documentation/security/ipe.rst
index 5eb3e6265fbd..4490aed5918a 100644
--- a/Documentation/security/ipe.rst
+++ b/Documentation/security/ipe.rst
@@ -442,5 +442,5 @@ IPE has KUnit Tests for the policy parser. Recommended kunitconfig::
CONFIG_SECURITY_IPE_KUNIT_TEST=y
In addition, IPE has a python based integration
-`test suite <https://github.com/microsoft/ipe/tree/test-suite>`_ that
+`test suite <https://github.com/Integrity-Policy-Enforcement/ci>`_ that
can test both user interfaces and enforcement functionalities.
--
2.55.0
next prev parent reply other threads:[~2026-10-03 2:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 2:51 [PATCH 0/6] ipe: cleanups, an audit fix and updated links Fan Wu
2026-10-03 2:51 ` [PATCH 1/6] ipe: constify token_default() Fan Wu
2026-10-03 2:56 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 2/6] ipe: use designated initializers for audit name tables Fan Wu
2026-10-03 2:59 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 3/6] ipe: check parser token table sizes Fan Wu
2026-10-03 2:56 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 4/6] ipe: correct policy text ownership comment Fan Wu
2026-10-03 2:57 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 5/6] ipe: fix enforcement audit Fan Wu
2026-10-03 2:55 ` sashiko-bot
2026-10-03 2:51 ` Fan Wu [this message]
2026-10-03 2:55 ` [PATCH 6/6] ipe: update the project and test suite links sashiko-bot
2026-10-06 16:59 ` [PATCH 0/6] ipe: cleanups, an audit fix and updated links Fan Wu
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=20261003025135.3666767-7-wufan@kernel.org \
--to=wufan@kernel.org \
--cc=linux-security-module@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox