[website] branch master updated: Update errors in footnotes.

Scott Cantor cantor.2 at osu.edu
Wed Mar 15 10:01:01 EDT 2017


This is an automated email from the git hooks/post-receive script.

scantor pushed a commit to branch master
in repository website.

The following commit(s) were added to refs/heads/master by this push:
       new  0f4c5ff   Update errors in footnotes.
0f4c5ff is described below

commit 0f4c5ffe21fc55be7addd29de824f2619f33c680
Author: Scott Cantor <cantor.2 at osu.edu>
AuthorDate: Wed Mar 15 10:00:58 2017 -0400

    Update errors in footnotes.
---
 community/advisories/secadv_20170315.txt | 31 +++++++++++++++----------------
 1 file changed, 15 insertions(+), 16 deletions(-)

diff --git a/community/advisories/secadv_20170315.txt b/community/advisories/secadv_20170315.txt
index 93676e3..b15bf8e 100644
--- a/community/advisories/secadv_20170315.txt
+++ b/community/advisories/secadv_20170315.txt
@@ -37,7 +37,7 @@ Recommendations
 ===============
 All deployers should upgrade to V3.3.1 at the earliest opportunity.
 
-The Release Notes [2] document describes an additional step that applies to a
+The Release Notes [1] document describes an additional step that applies to a
 very small number of deployers. The vast majority are not using this feature,
 but anyone who has defined custom flow "events" in login, interceptor, or subject
 canonicalization flows will need to do a bit of additional work, as described
@@ -46,7 +46,7 @@ there.
 Any deployers relying on business rules of the sort described above in which
 service requirements alone do not dictate the expected policy decision on how
 authentication must be performed should consider deploying an "interceptor"
-flow, possibly via the delivered "context-check" feature [3], to perform a final
+flow, possibly via the delivered "context-check" feature [2], to perform a final
 check that the authenticated Subject meets the requirements of the intended
 policy. An example of this has been added to the documentation. This greatly
 reduces the possibility that future flaws in the software might lead to
@@ -65,23 +65,22 @@ Credits
 The University of Chicago
 Unicon, Inc.
 
-
 [1] https://wiki.shibboleth.net/confluence/display/IDP30/ReleaseNotes
 [2] https://wiki.shibboleth.net/confluence/x/tABSAQ
 
 -----BEGIN PGP SIGNATURE-----
 
-iQIcBAEBCgAGBQJYyT0yAAoJEDeLhFQCJ3liJ+gP/0x8+X72J1YpHXVpKXpS/Xsp
-vAdXm9OsqsBv5D53hvX8cflQxSPYzaF9qciSA2Pp8+tzq5DqGHS8nlWKroMJloQz
-BLESz6DYtIdKN4slWfF6ogkmfckOEI2wBabPDTPNiM5+d3vDpKO6W1znQmTkc4/p
-IenbFKXf5CAMwICHtndEo+lpCC5g9WQ+OnhFgTr3XXDyiomxqhzQuZjQKv1t3L+/
-kfj6GqYpYcsVzwYCCJe4i8tp3vnUuYWD9FEj97LTOMHcDFzjWPD6t/5VXnoFf4WF
-YoenvN8EC0j+UKeTSmD7qffCcUtYmSn18gPp2t5Tbm5/cq+31t7y4MXK/s4dj8I6
-i8kCdpom8vCrsqBbepHBzt4gl93RIC+qio7HVL3Yvm5072io1HWpOebiG4W191ws
-7+WjjdFhla3w+X6Grd1E2sGfLOcpLNHIokMP4nBv3ttgyXqcsNDvOGuvI3hNYrtq
-iPWjbhw6K6V7oohaezYJRRsuWATOuqybs9o6S1avOZsCDG90ZP16nBw7FuFtxooi
-2eSjUfWURx3I8mRUB0ianv1aURAqWjFBTy30HezsanAlVaQxCq5VI9A0atJ02I6q
-7DVkNjJd8DW+ULKBb7ZKYwaK6l7Ft4Rjlr3cMDHutfGURv3NI/RRqFLz6Gh6Rprb
-JWNhL8yjhnLNtP9uQGIn
-=TQfF
+iQIcBAEBCgAGBQJYyUjpAAoJEDeLhFQCJ3liRmcQAMKRRSwHeop7oMg+M7+Lj6l2
+a3VHPcOZMQ8rkKkEp1QG2fdgtWUuzvE+/HoLokL+GqH48vv3Zsf50PRnlyCcUufI
+cUQ+kYyWBwGCvl07gUWDHAYo2nccRUU7dNIQh/vz6vUuSSOyafWcOX9W4XE+hrbV
+DbzwwHHGOTWIZ1cYxaciUD8zazJJJ+2sReRznWnlaOcTYEHtDGdiH4Dqp8lRkwep
+weMv3mvSkL0jjCTLvkl6R+aedKqJ5if38tzPYXL68/kNJ6nz/AguAecffwmG39pk
+oBrSfTBP9CT/p2bSg/GxDBVvsg+q1raj/S9oXCRvjVnQWp0fHdwiSbmzKtzluVKD
+FldnAvUAkp94RmVErwFwcNMElY2z3qgzpnkAYDSyMfchOMiNCEOV8uHU3o9l1jOA
+JCOoTfB2qWMX2lD6R3qh4DjYo6MTcbHnfHylYZqt1vTYBDiNtHp0C2kv4Sl+LpdQ
++XCm/vabFkW5u8SY/y7J6eMIrHU5+mB5lj5/Tv4hc6JQ2YcOCU5+zZyxse5vh9Qb
+h0//2UoV3jZdpMjVDucjyAqOazP4GC2kaHuTSGTE+22uiw4K8ohZlh2g+ONcKANT
+OaxD5cLQuktNawQAua+Dqt/cYS4z8oDoalTYZiZObnxAbOkpH3LxiPJNdezK5paN
+O4YEYK6kYMCWloaxz0gN
+=O1Uh
 -----END PGP SIGNATURE-----

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.


More information about the commits mailing list