Tiny Core Extensions > TCE 2.x

openssl-0.9.8

(1/2) > >>

Jason W:
Openssl updated to 0.9.8n and extension name is now openssl-0.9.8.tcz.  WIll be last name change for the 0.9.8 series.  For those with existing tce directories, use Appsaudit to update dep files, then simply install openssl-0.9.8.tcz extension, remove openssl-0.9.8m.tcz and reboot.


--- Code: ---Title:          openssl-0.9.8-dev.tcz
Description:    Openssl development files.
Version:        0.9.8n
Author:         OpenSSL Project
Original-site:  http://www.openssl.org/
Copying-policy: OpenSSL License:  http://www.openssl.org/source/license.html
Size: 1.5M
Extension_by:   Jason W
Comments:       Requires the openssl-0.9.8m.tcz extension and compiletc.
This extension is PPI compatible.
Change-log:     2008/07/30 First version 0.9.8h
2008/12/03 Rebuilt for i486 and size.
2009/09/09 Updated to 0.9.8k.
2010/02/27 Updated to 0.9.8m
Current: 2010/04/03 Updated to 0.9.8n and removed patchlevel from name.


--- End code ---


--- Code: ---Title:          openssl-0.9.8-doc.tcz
Description:    The Open Source toolkit for SSL/TLS docs
Version:        0.9.8n
Author:         OpenSSL Project
Original-site:  http://www.openssl.org/
Copying-policy: OpenSSL License:  http://www.openssl.org/source/license.html
Size: 946M
Extension_by:   Jason W
Comments:       ----------
Change-log:     2008/07/30 First version 0.9.8h
        2008/12/11 Rebuilt for i486, size, cramfs.
2010/02/27 Updated to 0.9.8m
Current: 2010/04/03 Updated to 0.9.8n and removed patchlevel from name.


--- End code ---


--- Code: ---Title:          openssl-0.9.8.tcz
Description:    The Open Source toolkit for SSL/TLS
Version:        0.9.8n
Author:         OpenSSL Project
Original-site:  http://www.openssl.org/
Copying-policy: OpenSSL License:  http://www.openssl.org/source/license.html
Size: 1.1M
Extension_by:   Jason W
Comments:       ----------
Change-log:     2008/07/30 First version 0.9.8h
        2008/12/11 Rebuilt for i486, size, cramfs.
2010/02/27 Updated to 0.9.8m
Current: 2010/04/03 Updated to 0.9.8n and removed patchlevel from name.


--- End code ---

maro:
Jason: I believe there is a tiny, but harmless issue with the startup script. At installation time one gets:
--- Code: ---mkdir: cannot create directory '/usr/local/etc/ssl/private': File exists
mkdir: cannot create directory '/usr/local/etc/ssl/certs': File exists

--- End code ---

Looking into the script I believe it is meant to be
    [ -d /usr/local/etc/ssl/private ] || mkdir /usr/local/etc/ssl/private
    [ -d /usr/local/etc/ssl/certs ] || mkdir /usr/local/etc/ssl/certs
instead of the [ -d ... ] && mkdir ... No harm done, since the directories should always exist, as they are part of the extension.

Jason W:
Yeah, it was meant to check for existence and create if not there.  I will fix it.

Thanks.

maro:
I just noticed that 'openssl-0.9.8o' has been released. Might be worth an update for 2.x at some stage.

Furthermore (even though this is the 2.x section) I wonder whether 3.x should aim to use version 1.0.0a. According to the announcement: "... We consider OpenSSL 1.0.0a to be the best version of OpenSSL available and we strongly recommend that users of older versions upgrade as soon as possible. ...". I guess now might be a good time to take the plunge, even though it could result in a fair number of rebuilds for 3.x.

althalus:

--- Quote from: maro on June 08, 2010, 08:16:45 PM ---I just noticed that 'openssl-0.9.8o' has been released. Might be worth an update for 2.x at some stage.

Furthermore (even though this is the 2.x section) I wonder whether 3.x should aim to use version 1.0.0a. According to the announcement: "... We consider OpenSSL 1.0.0a to be the best version of OpenSSL available and we strongly recommend that users of older versions upgrade as soon as possible. ...". I guess now might be a good time to take the plunge, even though it could result in a fair number of rebuilds for 3.x.

--- End quote ---

I think the best way would be to have two openssl extensions in the 3.x repo - one for 0.9.8 and one for 1.0.0 - People can migrate their old extensions gradually, and the TC team could knock back any new extensions where the maintainer has been silly enough to build against  the older 0.9.8 instead of the "recommended" version.

(This could probably be split out into it's own topic...)

Navigation

[0] Message Index

[#] Next page