Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

Listing 3-1 is shown to demonstrate the µC/FTPs module capabilities in standard mode. That code simply initializes µC/TCP-IP, µC/FS, and µC/FTPs in standard mode.

Listing 3-1 Example code in standard mode

 

L3-1(1) Initialize the µC/TCP-IP protocol suite.

L3-1(2) Initialize the file system.

L3-1(3) Initialize the µC/FTPs module with secure mode disabled. The module is then ready to accept standard requests from clients.

Listing 3-2 is shows the µC/FTPs module capabilities in secure mode. That code simply show how initialize µC/TCP-IP and µC/FS then µC/FTPs in secure mode. A secure FTP server configuration structure, has to be initialized before µC/FTPs can be initialized.

Listing 3-2 Example code in secure mode

L3-2(1) Initialize the µC/TCP-IP protocol suite.

L3-2(2) Initialize the file system.

L3-2(3) Initialize the server public key certificate. The FTPs_SECURE_CFG structure only stores a pointer to the public key meaning that the public key array must be maintained in memory throughout the execution of the FTP server.

L3-2(4) Initialize the length of the public key certificate.

L3-2(5) Format of the key certificates. Supported formats are PEM and DER.
The value can either be:
NET_SOCK_SECURE_CERT_KEU_FMT_PEM or
NET_SOCK_SECURE_CERT_KEU_FMT_DER

L3-2(6) Initialize the server private key certificate. The FTPs_SECURE_CFG structure only stores a pointer to the private key meaning that the public key array must be maintained in memory throughout the execution of the FTP server.

L3-2(7) Initialize the length of the private key certificate.

L3-2(8) Initialize the µC/FTPs module with secure mode enabled. The module is then ready to accept secure requests from clients.

L3-2(9) Flag to set if the public certificate is chained to another one.

  • No labels