Here are my tests:
Linux 32-bit:
- ZIP file is OK and can be uncompressed
- MD5, SHA1 are OK [1]
- ZIP ASC is OK (signature from Kay Schenk)
- Library ASC is OK (signature from Ariel Constenla-Haile)
Linux 64-bit:
- ZIP file is OK and can be uncompressed
- MD5, SHA1 are OK [1]
- ZIP ASC is OK (signature from Kay Schenk)
- Library ASC is OK (signature from Ariel Constenla-Haile)
Mac OSX:
- ZIP file is OK and can be uncompressed
- MD5, SHA1 are OK [1]
- ZIP ASC is OK (signature from Kay Schenk)
- Library ASC is OK (signature from Ariel Constenla-Haile)
However, after rewriting the files (of course without to modify the hash
values itself) the comparsion was OK.
@Kay:
I've uploaded the sha256 hash files as suggested. Do you mind when I
overwrite the other hash files with the ones I've created? Then all have
the same format.
Furthermore, I've read the Readme's for Linux [2] and Mac. As I didn't
wanted to simply overwrite your work, I've attached the modified
versions. So, you can review them first or I can overwrite them if you
don't mind.
[1] The files are not well formatted for the "md5sum" and "sha1sum"
commands. They need the following format:
<hash value><space><space><file name>
[2] The Readmes for Linux 32-bit and 64-bit are the same. I've just
attached the one for 32-bit.
Marcus
Am 08/12/2016 06:21 PM, schrieb Kay Schenk:
On Thu, Aug 11, 2016 at 3:27 PM, Marcus<marcus.m...@wtnet.de> wrote:
Am 08/11/2016 09:50 PM, schrieb Kay sch...@apache.org:
On 08/09/2016 02:12 PM, Kay Schenk wrote:
[top posting]
I'm in the process of trying to "sync" instructions for Linux32,
Linux64, and MacOSX at the moment. As far as instructions on the actual
HOTFIX page, we need to have just a "general" instruction for ALL zips
that simply says -- "Unzip this package to some folder of your choosing
and read the README that's included." Everything else should be in the
various READMEs for each platform.
I should be done with all edits by this evening for a final review
before zipping and signing.
Ok, I've now moved on to creating zip files, etc for Linux32, Linux64
and Mac.
My openssl version on does NOT supply digest sha256. Is it OK to use
sha1? MD5 already computed for each of these.
I like to have it consistent for all platforms. Therefore I'll check the
ZIPs and deliver the sha256 hash files.
Marcus
Thanks a bunch Marcus!
On 08/05/2016 09:28 AM, Dennis E. Hamilton wrote:
Branching off the part that is not about the Windows 4.1.2-patch1
[TESTING].
-----Original Message-----
From: Marcus [mailto:marcus.m...@wtnet.de]
Sent: Thursday, August 4, 2016 15:52
To: dev@openoffice.apache.org
Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
Am 08/05/2016 12:26 AM, schrieb Kay Schenk:
[ ... ]
hmmm...well no zips for Mac, Linux32, or Linux 64 -- yet.
Should we get started on these?
it depends what we want that they should contain. The ZIP file for
Windows contains a LICENSE and NOTICE file as well as an ASC file for
the DLL. As it is only a patch IMHO we don't need to provide another
LICENSE and NOTICE file which is already available in the OpenOffice
installation. Also the ASC is not necessary as we provide it already
(together with MD5 and SHA256) for the whole ZIP file.
[orcmid]
I think there is a misunderstanding. Two matters:
1. The use of LICENSE is required by the ALv2 itself, and the ASF
practice is to include NOTICE as well on binary distributions. The patch
qualifies, especially when it is moved to general distribution. It is also
easy and harmless to provide.
2. The reason for preserving the .asc on the shared-library binary is
because it authenticates with respect to who produced it and establishes
that it has not been modified as supplied in the package (or as the result
of some glitch in creation of the Zip). It provides a level of
accountability and, also, auditability.
Even though few people will check all of these, they remain possible to
be checked. Since this is a matter of security vulnerabilities and
involves elevation of privilege to perform, I believe it is important to
demonstrate diligence and care, so that users have confidence in this
procedure to the extent they are comfortable. Also, if it becomes
necessary to troubleshoot a problem with these patch applications, we have
the means to authenticate what they are using to ensure there are no
counterfeits being offered to users.
That means that only the README and library file remains.
When the README for Windows keep its length then I don't want to copy
this on the dowload webpage. ;-)
So, when we put the README for all platforms in their ZIP files then we
can just put a pointer to it on the download webpage and thats it.
[orcmid]
Yes, that seems like a fine idea. The README can be linked the same
way the .md5, .sha256, and .asc are linked.
Also, the README may become simpler if we can link to some of the
information and not have so much detail in the README text itself. It
might even be useful to have an .html README for that matter. But that is
all extra. Right now I think we want to get into the testing and see how
to smooth what we have.
PS: A friend of mine is looking into the MacOSX situation. He points
out that one can use the Finder to do the job without users having to use
Terminal sessions. I don't have further information at this time.
PPS: The inclusion of scripts that do the job is also worthy of
consideration, perhaps making it unnecessary to build executables. I will
be looking at finding a .bat file that works safely for the Windows case.
That can make the instructions much shorter :).
To cut a long story short:
I would say yes for a ZIP file for every platform.
[ ... ]
General
-------
This hotfix ZIP file consists of the following files:
* LICENSE.txt - Information about the Apache License v2
* Linux32.README.txt - The file you are reading
* NOTICE.txt - Software notes
* libtl.so - Patch file that you will need to install
* libtl.so.asc - Public signature file of the developer who built the
patch file
You can use whatever GPG tools you have to verify the signature against the
information provided in the Apache OpenOffice KEYS file:
https://dist.apache.org/repos/dist/release/openoffice/KEYS
Prerequisites
-------------
Download the hotfix ZIP file to a location on your PC where it can be used and
its content extracted.
Example:
User Jane downloaded and extracted the hotfix ZIP file from her browser window
and saved it in a folder called "Downloads". The full path is:
/home/jane/Downloads
Installation Instructions
-------------------------
This file provides basic instructions for installing the patched file
"libtl.so" into your existing Apache OpenOffice installation. You will need to
do this replacement using a console (terminal) window and will likely need to
use "root" (administrator) access to your system.
0. Make sure OpenOffice is not being used.
1. Open a console window and login as root with the following command:
$ su -
2. Locate where Apache OpenOffice is installed on your system:
a) If you already know where Apache OpenOffice is located on your
system, navigate
to that directory. Example:
$ cd /opt/openoffice4
b) If you do not know this, you can use your package manager (e.g.,
RPM) to find
this, or use the "locate" command. Examples:
$ rpm -ql openoffice | grep libtl.so
$ locate openoffice | grep libtl.so
The commands show you the "program" sub-directory where Apache
OpenOffice is
installed.
For illustration, let's assume "/opt/openoffice4" is the directory
location of
OpenOffice. Navigate to the "program" sub-directory:
3. Navigate to the "program" sub-directory of your Apache OpenOffice
installation:
$ cd /opt/openoffice4/program
4. List the files in the Apache OpenOffice program sub-directory:
$ ls
You should see a file listed as "libtl.so".
5. Make a backup of the existing file by renaming it.
You can leave this where it is if you like:
$ mv libtl.so libtl.so.org
6. Copy the new "libtl.so" provided by this hotfix to the "program"
sub-directory.
Use your download folder with the saved and extraced ZIP file to copy
it to the
"program" sub-directory. Use the following command to copy the file:
$ cp -p /home/jane/Downloads/libtl.so .
(the last dot "." is an abbreviation for the current directory)
7. Verify that the "libtl.so" got placed in the "program" sub-directory.
$ ls -al
This will allow you to verify permission settings on the new file.
Important:
If it is NOT listed as "-r--r--r-- 1 root root", go to Step 8.
8. Change file ownership and permissions.
To correct the ownership and permission settings on the new "libtl.so",
execute both
commands still in the console window as root in the "program"
sub-directory:
$ chown root:root libtl.so
$ chmod 755 libtl.so
9. Now the patch work is done and you can exit the console window:
$ exit
10. Start Apache OpenOffice as you normally would as a non-privileged user.
General
-------
This hotfix ZIP file consists of the following files:
* LICENSE.txt - Information about the Apache License v2
* MACOSX.README.txt - The file you are reading
* NOTICE.txt - Software notes
* libtl.dylib - Patch file that you will need to install
* libtl.dylib.asc - Public signature file of the developer who built the
patch file
You can use whatever GPG tools you have to verify the signature against the
information provided in the Apache OpenOffice KEYS file:
https://dist.apache.org/repos/dist/release/openoffice/KEYS
Prerequisites
-------------
Download the hotfix ZIP file to a location on your PC where it can be used and
its content extracted. In Mac OS X the typical folder is "Downloads". But you
can use any other folder.
Installation Instructions
-------------------------
This file contains two sets of instructions. The first (I) outlines how to
install the new library file using a Terminal window and the command line. The
second (II) outlines how to install the new library file using the Finder. Both
sets of instructions assume you downloaded the zip file and "unzipped" it
directly into Downloads.
I. Using the Terminal window.
I.1. Directions for updating the file using a Terminal window.
These directions assume (1) familiarity with using the command line in
a Terminal
window; and (2) that the user has administrator privileges.
I.2. Make sure that OpenOffice is not running.
I.3. Open the Finder App (or another file manager of your choice).
I.4. Determine the installation path.
Locate the installation path of the OpenOffice program files. The
default path is
"/Applications/OpenOffice.app/Contents/program/").
I.5. Make a backup of the existing file by renaming it.
Rename the old file "libtl.dylib" to "libtl.dylib.original".
You can keep the file "libtl.dylib.original" as a backup as long as you
want.
I.6. Copy the new file "libtl.dylib".
From the extracted ZIP file copy the file "libtl.dylib" to the
"/Applications/OpenOffice.app/Contents/program/" folder. You need
Administrator
privileges for this.
In a terminal window these commands will accomplish the file copy. It
is assumed
that you downloaded and extracted the contents of the ZIP file directly
into
"Downloads":
$ cd ~/Downloads
$ sudo cp -v libtl.dylib /Applications/OpenOffice.app/Contents/program
II. Using the Finder App - or another file manager of your choice.
II.1. Directions for updating the file without using a Terminal window.
These instructions assume:
(1) that the user account has Administrator privileges; and
(2) that the file "libtl.dylib" was saved to the Downloads folder.
II.2. In Finder select the "Go" menu on the Application menu bar (at the top of
the
screen) and open a window to the Downloads folder.
II.3. In Finder open another Finder window and in the sidebar select the
Applications folder:
Do the follwoing steps:
- Hold down the "Control" key and select the OpenOffice application.
- Select "Show Package Contents" from the drop-down menu.
- Open the Contents folder now displayed in the Finder window.
- Select and open the "program" folder displayed in the Finder window.
- Scroll through the list of files shown and find "libtl.dylib".
- Hold down the "Control" key and select the "libtl.dylib" file.
- Select "Duplicate" from the drop-down menu.
(a file named "libtl copy.dylib" is created)
- Select the back button "<" from the Finder window top menu.
(the Finder displays the list of files and folders in the Contents
folder)
II.4. Select the Finder window showing the "Downloads" folder contents.
Do the following steps:
- Hold down the "Control" key and select the "libtl.dylib" file.
- Select "Copy 'libtl.dylib'" from the drop-down menu.
- Select the other Finder window showing the list of files in the
Contents folder.
- Hold down the "Control" key and select the "program" folder.
- Select "Paste Item" from the drop-down menu.
- A window appears with the message:
"An older item named "libtl.dylib" already exists in this location.
Do you want to
replace it with the newer one you're moving?"
- Select the "Replace" button.
Now the patch work is done and you can exit any opened Terminal window and
Finder.
Start Apache OpenOffice as you normally would as a non-privileged user.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
