| 1 | For MeV to work as a Java Webstart application, the JAR |
|---|
| 2 | files in the ./resources/jar must be signed. The currently |
|---|
| 3 | checked in JAR files have already been signed, so there is |
|---|
| 4 | no need to do this again unless MeV itself needs to be |
|---|
| 5 | updated or if the current certificate has expired. |
|---|
| 6 | Since this is a somewhat complex task, we have tried to make |
|---|
| 7 | easier. |
|---|
| 8 | |
|---|
| 9 | Follow this procedure (for updating MeV): |
|---|
| 10 | |
|---|
| 11 | 1. Delete all the existing JAR files in the ./resources/jar |
|---|
| 12 | directory. |
|---|
| 13 | 2. Copy all JAR files from the MeV distribution into the |
|---|
| 14 | ./resources/jar directory |
|---|
| 15 | 3. Run 'ant fixjars' (*) |
|---|
| 16 | 4. Run 'ant signjars' |
|---|
| 17 | 5. Commit the changes to the subversion repository. |
|---|
| 18 | |
|---|
| 19 | Follow this procedure (for re-signing with a new certificat): |
|---|
| 20 | |
|---|
| 21 | 1. Generate a new certificate as desribed below. |
|---|
| 22 | 2. Set lazy="false" for the <signjar> action in build.xml |
|---|
| 23 | 3. Run 'ant signjars' |
|---|
| 24 | 4. Revert back to lazy="true" |
|---|
| 25 | 5. Commit the changes to the subversion repository. |
|---|
| 26 | |
|---|
| 27 | -------------------------------------------------------- |
|---|
| 28 | * There is currently a problem with the 'magetab-parser.jar' |
|---|
| 29 | and 'goose.jar' files. |
|---|
| 30 | |
|---|
| 31 | The 'magetab-parser.jar' file contains identical copies of |
|---|
| 32 | several files and the signing tool doesn't allow this. The |
|---|
| 33 | 'fixjars' target will re-package the JAR file and remove |
|---|
| 34 | the extra copies. |
|---|
| 35 | |
|---|
| 36 | The 'goose.jar' file has already been signed by another |
|---|
| 37 | authority. To reduce the number of warnings a user has to |
|---|
| 38 | get through we remove the existing signature and replace |
|---|
| 39 | it with our own. |
|---|
| 40 | -------------------------------------------------------- |
|---|
| 41 | |
|---|
| 42 | |
|---|
| 43 | Note! |
|---|
| 44 | |
|---|
| 45 | The mev-base.key is the self-signed certificate that we have |
|---|
| 46 | used to sign the JAR files. It has the following properties: |
|---|
| 47 | |
|---|
| 48 | Alias: mev-base |
|---|
| 49 | Password: mev-base |
|---|
| 50 | Name: BASE Development team |
|---|
| 51 | Organizational unit: BASE Development team |
|---|
| 52 | Organization: Lund University |
|---|
| 53 | City: Lund |
|---|
| 54 | State: Sweden |
|---|
| 55 | Country code: SE |
|---|
| 56 | |
|---|
| 57 | To re-generate the keystore execute the following command: |
|---|
| 58 | |
|---|
| 59 | keytool -genkey -validity 1000 -alias mev-base -keypass mev-base -keystore mev-base.key |
|---|
| 60 | --------------------------------------------------------------- |
|---|
| 61 | |
|---|
