From 32a2a799fda8373e118cf7bd61a09f15c1895cf1 Mon Sep 17 00:00:00 2001
From: gh-actions
Date: Thu, 25 Apr 2024 14:41:57 +0000
Subject: [PATCH] Update 1.3 userdocs
---
public/docs/user/1.3/_sources/signNverify.rst.txt | 2 +-
public/docs/user/1.3/signNverify.html | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/public/docs/user/1.3/_sources/signNverify.rst.txt b/public/docs/user/1.3/_sources/signNverify.rst.txt
index 2e14b220..00cc650c 100644
--- a/public/docs/user/1.3/_sources/signNverify.rst.txt
+++ b/public/docs/user/1.3/_sources/signNverify.rst.txt
@@ -273,7 +273,7 @@ As well as the default behaviour, which signs all objects, fine-grained
control of signing is possible.
If you ``sif list`` a SIF file you will see it is comprised of a number
-of objects. Each object has an ``ID``, and belongs to a ``GROUP``.
+of objects. Each object has an ``ID``, and belongs to a ``GROUP``. Since signatures are *applied* to objects, they have an ``ID`` but not a ``GROUP``.
.. code::
diff --git a/public/docs/user/1.3/signNverify.html b/public/docs/user/1.3/signNverify.html
index 31127b6e..d8439e16 100644
--- a/public/docs/user/1.3/signNverify.html
+++ b/public/docs/user/1.3/signNverify.html
@@ -369,7 +369,7 @@ Advanced Signing - SIF IDs and Groups
+of objects. Each object has an ID
, and belongs to a GROUP
. Since signatures are applied to objects, they have an ID
but not a GROUP
.
$ apptainer sif list my_container.sif
------------------------------------------------------------------------------