[
https://issues.apache.org/jira/browse/RAMPARTC-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573579#action_12573579
]
S.Uthaiyashankar commented on RAMPARTC-74:
------------------------------------------
If we pass node_to_be_encrypted(B, in example given above) as well to
oxs_token_build_encrypted_data_element, then we can use
axiom_node_insert_sibling_before/axiom_node_insert_sibling_after to attach the
EncryptedData before/after node_to_be_encrypted. Thoughts?? Any comments are
appreciated.
> wrong encryption with oxs_token_build_encrypted_data_element
> ------------------------------------------------------------
>
> Key: RAMPARTC-74
> URL: https://issues.apache.org/jira/browse/RAMPARTC-74
> Project: Rampart/C
> Issue Type: Bug
> Components: Rampart-core
> Reporter: Lukas JOSEFIK
> Assignee: Ruchith Udayanga Fernando
>
> if you encrypt data and use oxs_token_build_encrypted_data_element, there can
> be problem with signed encrypted data verification. Problem is that
> oxs_token_build_encrypted_data_element calls axiom_element_create, which adds
> ecnrypteddata element to the end of children list. but if we consider element
> X and we want encrypt subelement B(<X>0x0a<B>0x0a<X>), encryption ends with
> <X>0x0a0x0a<EncryptedData...><X>. After decryption the data looks
> <X>0x0a0x0a<B><X> and verification fails...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
