RFC 2773:Encryption using KEA and SKIPJACK
RFC-Ref

encryption


Click on the red underlined text to get to the source

... Key Exchange Algorithm (KEA) in conjunction with the SKIPJACK symmetric encryption algorithm. ...
... session parameter negotiation -- in particular, encryption keys and attributes; ...


... FTP entities may use KEA to give mutual authentication and establish data encryption keys. We specify a simple token format and set of exchanges to deliver these services ...
... concatenation is " || ". Decryption of encrypted data and certification path validation is ...
... Base64( Certa || Ra || WMEK || IV || Encrypt( Label-Type || Label-Length || Label-List || pad || ICV ...
... for this FTP session may be transferred to the server encrypted in the MEK. As shown in Figure 2, the security label data is formatted ...
... cryptographic block size, padding shall be performed as follows. The input to the SKIPJACK CBC encryption process shall be padded to a multiple of 8 octets. Let n be the length in octets of the input. ...
... a multiple of 8 octets in length. This pad technique is used whenever SKIPJACK CBC encryption is performed. ...
... ICV technique is used in conjunction with SKIPJACK CBC encryption to provide data integrity. ...
... sequence number, padding, and ICV are appended to each command prior to encryption. ...
... ENC Base64(Encrypt("PBSZ 65535" || SEQ ...
... ICV )) --> <-- 632 Base64(Encrypt("200" || SEQ || pad || ICV ...
... ICV)) ENC Base64(Encrypt("USER yee" || SEQ ...
... ICV)) --> <-- 632 Base64(Encrypt("331" || SEQ || pad || ICV ...
... ICV)) ENC Base64(Encrypt("PASS fortezza" || SEQ ...
... ENC Base64(Encrypt("PROT P" || SEQ ...
... ICV)) --> <-- 632 Base64(Encrypt("200" || SEQ || pad || ICV ...
... At this point, files may be sent or received with encryption and integrity services in use. If encryption ...
... encryption and integrity services in use. If encryption is used, then the first buffer will contain the token ...
... buffer will contain the token followed by enough encrypted file octets to completely fill the buffer (unless the file is too short to ...
... fill the buffer). Subsequent buffers contain only encrypted file octets. All buffers are completely full except the final buffer ...
... ENC Base64(Encrypt( ("RETR foo.bar") || ...
... ICV)) --> <-- 632 Base64(Encrypt("150" || SEQ || pad || ICV ...
... Pre-encrypted File Support ...
... In order to support both on-the-fly encryption and pre-encrypted files, a token ...
... In order to support both on-the-fly encryption and pre-encrypted files, a token is defined for carrying a file encryption key ...
... encrypted files, a token is defined for carrying a file encryption key (FEK). To prevent truncation and ensure file integrity, the token ...
... session TEK. The token is encrypted in the session TEK ...
... the plaintext IV used to encrypt the remainder of the token. The token ...
... token. The token requires its own encryption IV because it is transmitted across the data channel ...
... hashes for files in the file system is a local implementation matter; however, it is suggested that if a file is pre-encrypted, then the FEK be wrapped in a local storage key. When the file is needed, the FEK is unwrapped using the local storage key, and then rewrapped in ...


... Key Type Usage TEK Encryption of token at the beginning of each file, also wraps the MEK and the FEK ...
... token at the beginning of each file, also wraps the MEK and the FEK MEK Encryption of command channel FEK Encryption ...
... Encryption of command channel FEK Encryption of the file itself (may be done out of scope of FTP) ...



Google
Web
RFC-Ref