diff --git a/doc/docbook/acegi.xml b/doc/docbook/acegi.xml index ed26e79b6e..6cfb56916a 100644 --- a/doc/docbook/acegi.xml +++ b/doc/docbook/acegi.xml @@ -117,19 +117,6 @@ Introduction - - Before You Begin - - For your security, each official release JAR of Acegi Security - has been signed by the project leader. This does not in any way alter - the liability disclaimer contained in the License, but it does ensure - you are using a properly reviewed, official build of Acegi Security. - Please refer to the readme.txt file in the root of - the release distribution for instructions on how to validate the JARs - are correctly signed, and which certificate has been used to sign - them. - - What is Acegi Security? diff --git a/readme.txt b/readme.txt index e8d91e2c59..4f81c6aa49 100644 --- a/readme.txt +++ b/readme.txt @@ -16,22 +16,7 @@ http://acegisecurity.org. SIGNED JAR FILES ------------------------------------------------------------------------------- -We strongly recommend that you verify the integrity of the JAR files included -in this release. You can do so using the following command: - - "jarsigner -verify -verbose -certs jar_file_name" - -Of course, replace the jar_file_name with "acegi-security-XXXXX.jar" or the -appropriate path to the Acegi Security JAR to be validated. - -Until further notice, all Acegi Security official releases are signed by: - - X.509, EMAILADDRESS=ben.alex@acegi.com.au, CN=Benjamin Peter Alex, GIVENNAME=Benjamin Peter, SURNAME=Alex - X.509, CN=Thawte Personal Freemail Issuing CA, O=Thawte Consulting (Pty) Ltd., C=ZA --> - -If the above certificate was not used, or the JAR was not validated, DO NOT -USE THE JAR. Please email the acegisecurity-developers list (contact details -are provided below) for further assistance. +JAR files are no longer signed. They were signed in releases 1.0.0 and earlier. ------------------------------------------------------------------------------- BUILDING