Security Library 1.04 Release note

Mar 1, 2010
Author: Sierra Wireless
Version: 1

1. NEW FEATURES.
2. SOFTWARE RELEASE DESCRIPTION.

2.1. Software Identification.
2.2. Compatibility.

3. KNOWN RESTRICTIONS.
4. INTERFACE MODIFICATIONS.
5. CORRECTIONS & IMPROVEMENTS.

1. New Features.

HTML Documentation: As well as PDF, the SSL and Jamming User Guides are available in HTML format. By installing the Security plug-in package with the Software Installer (e.g. Sierra Wireless Software Suite v2.34 Full Installer.exe) or with the Developer Studio, you can use the Developer Studio to surf dynamically into the documentation. Press “F1” to display the dynamic contextual help to launch research or to directly access to our SSL and jamming function indexation tables

Threshold Tuning: New API has been provided to tune the Mean Threshold value used by the Jamming Algorithm. This feature is available in beta stage. Please refer to the Interface modifications section below for the new APIs.

2. Software Release Description.

2.1. Software Identification.

Software Identification

Security 1.04

2.2. Compatibility.

Libraries compliant with

Open AT^® OS 6.20

Internet plug-in 5.30

3. Known restrictions.

Id	Description (What / When)	Impacted Domain	Impacted Sub Domain	Submitted Date
ANO47945	The following options of the GetOpts function don't work correctly or provide unintelligible results: WIP_COPT_PUB_KEY, WIP_COPT_EXT_CRITICAL, WIP_COPT_PUB_KEY_ALGO and WIP_COPT_SIG_ALGO. It is recommended not to use these options.			06/05/2008 16:43:23
ANO48185	TLS Ciphers are being used while SSLV3 version is used during channel creation. Though, the channel is created successfully as the client is able to handshake properly with the server but the underlying protocol used is not correct.			21/05/2008 11:05:59
ANO50375	In case of big transfer, customer should use smaller buffers or increase the internal SSL write buffer size to send its data			11/09/2008 13:57:41

4. Interface modifications.

This section lists the interfaces that have been modified from the Security 1.03.

API	Comment
s32 JammingDetectionSetMeanThreshold (s32 meanThresholdValue)	This API can be used to change the Mean Threshold value used by the Jamming Algorithm. This API takes Mean Threshold value to be set as input and return OK on success or ADL_RET_ERR_PARAM if the meanThresholdValue is out of range [0..63].
s32 JammingDetectionGetMeanTreshold (void)	This API gets the Mean Threshold value used by the Jamming Algorithm. This API takes nothing as input and returns the mean threshold value.

5. Corrections & Improvements.

Id	Description (What / When)	Impacted Domain	Impacted Sub Domain	Fixed in
CUS54456	SSL library does not forward PEER CLOSE event to user application. As a consequence, SSL resources are not released (even when forcing closure with wip_SSLClose()). Subsequent SSL socket opening could fail with backtrace "ADL get memory" leading to a reset.			Security 1.03
CUS51825 ANO50428	Data corruption is possible in first data exchanged between client and server using SSL channel			Security 1.02
CUS44486	If you are using an SSL socket and if an event WIP_CEV_ERROR is generated, the memory resources used by the SSL socket are not released even if a wip_close() is called. If there is not enough available memory, the trace "ADL Get memory error" and RESET is sent, when a try to open another SSL session is made. To avoid the RESET, use the adl_errSubscribe function to trap the error (however a reset is necessary to reopen an SSL session).			Security 1.01
ANO48105	When you are getting an HTTPS page through the GPRS bearer, It is possible to receive two WIP_CEV_PEER_CLOSE events instead of one.			Security 1.01
DEV48633	Customer cannot create their own WIP channel classes			Security 1.01
ANO48115	It is impossible to connect to a SSL server if WIP_COPT_ENCRYPTION and/or WIP_COPT_AUTHENTICATION are/is set to WIP_SSL_NULL.			Security 1.01

Comment

Forum