IPC@CHIP® RTOS-PPC – API Documentation

Header image

Main page


Release Notes – SC2x3 @CHIP-RTOS-PPC V1.70

The tickets are grouped by component and then sorted by type and ticket number.


RTOS - Config server
Ticket: #470
Component: RTOS - Config server
Type: defect
Summary: UDPCFGSRV does not allow flash image programming/ip configuration when long password is set
Description: Flash programming/IP configuration passwords that are 16 characters long (the documented maximal length) do not work. When such a password is configured the device does not allow flash programming/IP configuration even if the correct password is given.
Solution: Fixed.



Ticket: #454
Component: RTOS - Config server
Type: enhancement
Summary: Configuring a multi-home index via Chiptool should store this configuration in CHIP.INI
Description: Currently, when a multi-home index is configured via the Chiptool IP configuration, the made changes are not stored in the CHIP.INI. The configuration is volatile. We should store the new configuration so that it is applied automatically at next boot.
Solution: Implemented.




RTOS - File system
Ticket: #467
Component: RTOS - File system
Type: defect
Summary: File read can fail when same file is being written
Description: The wrong cluster will be read out when a previous read ended at the tail of a cluster (cluster boundary) and this was the end of that file at that time.

Then when more data is written to that file using some other file handle and another read is made with the same open file handle as the first read, what was the last cluster will be read again instead of data from the new cluster that some writer had just added.
Solution: When reading from a file, note when end of file has been reached, so that the cluster chain in the File Allocation Table (FAT) can be consulted on a subsequent read to see if any new cluster had been appended to that chain.




RTOS - IPsec/IKE/Crypt
Ticket: #462
Component: RTOS - IPsec/IKE/Crypt
Type: defect
Summary: RSA key cannot be read
Description: Some RSA keys cannot be read by the @CHIP-RTOS. Re-coding them with
openssl.exe rsa -in oldkey.pem -out newkey.pem
was a workaround for this problem.
Solution: Add handling for extracting RSA key data from a PKCS#8 format private key file. The oldkey.pem used this alternative private key format.




RTOS - TCP/IP
Ticket: #460
Component: RTOS - TCP/IP
Type: defect
Summary: Other tasks can be blocked during the SSL handshake
Description: During a tasks performs the SSL handshake, other tasks that also access the TCP/IP stack can get blocked during this period. Also Ethernet pings are not answered during this time.
Solution: 1) During long RSA modular exponent computations, set a "IN RSA" flag and then release the socket lock.
2) Prevent all socket API functions from locking this socket when the "IN RSA" flag for this socket is set. They will instead spin in a sleep loop, periodically polling for this flag to go away.
This solution allows the internal TCP/IP stack's timer task and device driver tasks to still access this socket during the time consuming RSA computation, thereby avoiding a TCP/IP stack deadlock during this period.



Ticket: #472
Component: RTOS - TCP/IP
Type: defect
Summary: SSL zero size certificate message contains garbage
Description: When the SSL client tries to reply with an empty certificate (ticket 425), it is sending garbage bytes in the SSL reply message.
Solution: Send zero certificate data bytes for empty certificate.



Ticket: #446
Component: RTOS - TCP/IP
Type: enhancement
Summary: Add option to skip certificate validation
Description: Should add an option to skip the certificate validation during the TLS handshake.
Solution: Extended the SSL_SessionOpt() API to allow for this certificate validation skipping.



Ticket: #447
Component: RTOS - TCP/IP
Type: enhancement
Summary: Accept DNS replies if neither "authoritative answer" nor "recursion available" flag is set
Description: The RTOS only accepts replies on DNS requests only if either the "authoritative answer" or the "recursion available" flag are set in the response header. However, some servers are able to provide a valid response without one of these two flags being set. The RTOS should accept answers from these servers.
Solution: Implemented.



Ticket: #448
Component: RTOS - TCP/IP
Type: enhancement
Summary: Call IP configuration callback also on default gateway change
Description: Should call IP configuration callback also on default gateway changes.
Solution: Implemented.



Ticket: #459
Component: RTOS - TCP/IP
Type: enhancement
Summary: Should increase the ephemeral Diffie-Hellman key size used by the SSL server
Description: We should increase the ephemeral Diffie-Hellman key size used by the SSL server, because recent OpenSSL versions do no longer accept keys below 1024 bits.
Solution: Implemented.



Ticket: #461
Component: RTOS - TCP/IP
Type: enhancement
Summary: Get details about SSL handshake error
Description: In case of an SSL handshake error, the function SSL_HandshakeComplete() delivers just a single error code. It would be helpful if another function can be called in this case, which delivers more details why the handshake has failed.
Solution: Added SSL_CheckProblem() API.




RTOS - Web server
Ticket: #445
Component: RTOS - Web server
Type: defect
Summary: User response headers no longer working from CGI page
Description: User response headers given in the fResponseHeadersPtr field, are no longer transmitted by the web server. This bug was introduced with ticket #432 on RTOS-PPC V1.50.
Solution: Fixed.



Ticket: #469
Component: RTOS - Web server
Type: defect
Summary: R2/R13 registers are not set correctly inside Webserver error/upload callbacks
Description: In contrast to normal CGI callbacks, the Web server error and upload handler callbacks are not installed with the correct program handle. The program handle holds a pointer to the program where this callback handler function is located. Due to this fact, the R2/R13 registers, which are used for the Small Data Areas (e.g. sdata, sbss), are not set correctly inside these callbacks. Accessing variables which are located inside the Small Data Areas will therefore fail from these callbacks.
Solution: Fixed.



Ticket: #449
Component: RTOS - Web server
Type: enhancement
Summary: Change the TLS cipher suites that the web server offers
Description: Should change the TLS cipher suites that the web server offers. Remove cipher suites that are regarded as insecure, like RC4.
Solution: Implemented.



Ticket: #471
Component: RTOS - Web server
Type: enhancement
Summary: Maximum BODY_SIZE value should be increased (again)
Description: The maximum value of the BODY_SIZE CHIP.INI parameter should be increased. There's no issue with the 64k border on the RTOS-PPC, so we should not limit it to such low values for no reason.
Solution: Increased the maximum adjustable value for BODY_SIZE from 65280 to 2097152.




RTOS - System
Ticket: #468
Component: RTOS - System
Type: enhancement
Summary: Should implement RTX_Task_Info_By_Id() API function
Description: Should implement the RTX_Task_Info_By_Id() API function, like known from the RTOS-LNX.
Solution: Implemented.








Top of page | Main page

Copyright © 2009 Beck IPC GmbH