[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: [wss] Comments on Swa profile interoperability.
From: Cayron, Serge
[mailto:Scayron@acord.org] I also don’t understand
the need for the requirement and solution described in http://www.oasis-open.org/archives/wss/200411/msg00061.html
(Swa issue 341) Why would we need to
take the Content-Transfer encoding MIME header into account at encryption time?
The Do we want to encrypt base64 content? This is what is suggested by the
phrase: a) in section 4.5.2 Encryption processing rules, adding a new
rule 4 between original rules 4 and 5.(and renumber the rules). This is a
modification of what Maneesh proposed: If we accept that
base64 encoding is the business of the MIME processor, then encryption should
always be done on (canonical) clear text. [MS] The
intent of the EncryptedData Encoding attribute was to preserve the original
C-T-E value of the pristine attachment part. It can be used by the decryptor to
restore the attachment to its original encoding after decryption. An attachment
is usually with a binary C-T-E after decryption. Using the encoding attribute,
it can be restored to, say, a base64 encoding. Maneesh
Sahu Actional
Corporation |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]